# flask-cors vulnerable to log injection when the log level is set to debug

Advisory record · `GHSA-84pr-m4jr-85g5`

- **Identifiers:** `GHSA-84pr-m4jr-85g5` · `CVE-2024-1681` · `PYSEC-2024-271`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-117](https://cwe.mitre.org/data/definitions/117.html)
- **Tags:** [Other injection](https://agentprime.io/advisories/tag/injection.md)
- **Published:** 19 Apr 2024
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 19 Apr 2024, 21:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `flask-cors` (PyPI): affected `<4.0.1`; fixed in `4.0.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> flask-cors versions before 4.0.1 are vulnerable to log injection when the log level is set to debug. An attacker who can send a GET request to the application can include a CRLF sequence in the request path to insert fake entries into the log file, which can hide other activity or confuse log analysis tools. Upgrade to flask-cors 4.0.1 or later.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.3 Medium, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`, from CNA (@huntr_ai)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0057, the 47th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:35 UTC: First seen by agentprime
- 31 Oct 2026, 14:35 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-84pr-m4jr-85g5)

## Sources

- [GitHub Advisory Database: GHSA-84pr-m4jr-85g5](https://github.com/advisories/GHSA-84pr-m4jr-85g5)
- [OSV: GHSA-84pr-m4jr-85g5](https://osv.dev/vulnerability/GHSA-84pr-m4jr-85g5)
- <https://nvd.nist.gov/vuln/detail/CVE-2024-1681>
- <https://github.com/corydolphin/flask-cors>
- <https://github.com/corydolphin/flask-cors/blob/40acc8092332dfed4bb54d7a4f89a6d479466de7/flask_cors/extension.py#L194>
- <https://github.com/pypa/advisory-database/tree/main/vulns/flask-cors/PYSEC-2024-271.yaml>
- <https://huntr.com/bounties/25a7a0ba-9fa2-4777-acb6-03e5539bb644>
- <https://lists.debian.org/debian-lts-announce/2025/05/msg00049.html>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-84pr-m4jr-85g5>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-84pr-m4jr-85g5/>. Everything for agents: <https://agentprime.io/llms.txt>.
