Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

GHSA-fjq3-5pxw-4wj4

HIGHFix: marshmallow-code/webargs@b9ee8b0

GHSA-fjq3-5pxw-4wj4 is a high-severity (CVSS 8.8) vulnerability in webargs. O3 Security confirms whether GHSA-fjq3-5pxw-4wj4 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Cross-Site Request Forgery in Webargs

Also known asCVE-2020-7965PYSEC-2020-156
Published
Apr 7, 2021
Updated
Nov 19, 2024
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 19, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
🐍webargs🐍webargs

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

flaskparser.py in Webargs 5.x through 5.5.2 doesn't check that the Content-Type header is application/json when receiving JSON input. If the request body is valid JSON, it will accept it even if the content type is application/x-www-form-urlencoded. This allows for JSON POST requests to be made across domains, leading to CSRF.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIwebargs5.0.0&&< 5.5.35.5.3
🐍PyPIwebargs6.0.0b1&&< 6.0.0b46.0.0b4

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for webargs. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update webargs to 5.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fjq3-5pxw-4wj4 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-fjq3-5pxw-4wj4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-fjq3-5pxw-4wj4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

flaskparser.py in Webargs 5.x through 5.5.2 doesn't check that the Content-Type header is application/json when receiving JSON input. If the request body is valid JSON, it will accept it even if the content type is application/x-www-form-urlencoded. This allows for JSON POST requests to be made across domains, leading to CSRF.
O3 Security · Impact-Aware SCA

Is GHSA-fjq3-5pxw-4wj4 in your dependencies?

O3 detects GHSA-fjq3-5pxw-4wj4 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.