Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
CRITICAL severity

GHSA-x92h-wmg2-6hp7

CRITICALFix: symfony/symfony@944e60f

GHSA-x92h-wmg2-6hp7 is a critical-severity (CVSS 9.8) vulnerability in symfony/http-foundation. O3 Security confirms whether GHSA-x92h-wmg2-6hp7 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Invalid HTTP method overrides allow possible XSS or other attacks in Symfony

Also known asCVE-2019-10913
Published
Dec 2, 2019
Updated
Nov 8, 2023
Affected
10 pkgs
Patched
10 / 10
Exploits
None indexed
Exploitation data as of Nov 8, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

10 pkgs affected
🐘symfony/http-foundation🐘symfony/http-foundation🐘symfony/http-foundation🐘symfony/http-foundation🐘symfony/http-foundation🐘symfony/symfony🐘symfony/symfony🐘symfony/symfony+2 more

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

Description

In Symfony before 2.7.51, 2.8.x before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, HTTP Methods provided as verbs or using the override header may be treated as trusted input, but they are not validated, possibly causing SQL injection or XSS. This is related to symfony/http-foundation.

Affected Packages

10 total 10 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistsymfony/http-foundation2.7.0&&< 2.7.512.7.51
🐘Packagistsymfony/http-foundation2.8.0&&< 2.8.502.8.50
🐘Packagistsymfony/http-foundation3.0.0&&< 3.4.263.4.26
🐘Packagistsymfony/http-foundation4.0.0&&< 4.1.124.1.12
🐘Packagistsymfony/http-foundation4.2.0&&< 4.2.74.2.7
🐘Packagistsymfony/symfony2.7.0&&< 2.7.512.7.51

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/http-foundation. 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 symfony/http-foundation to 2.7.51 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x92h-wmg2-6hp7 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-x92h-wmg2-6hp7 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-x92h-wmg2-6hp7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In Symfony before 2.7.51, 2.8.x before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, HTTP Methods provided as verbs or using the override header may be treated as trusted input, but they are not validated, possibly causing SQL injection or XSS. This is related to symfony/http-foundation.
O3 Security · Impact-Aware SCA

Is GHSA-x92h-wmg2-6hp7 in your dependencies?

O3 detects GHSA-x92h-wmg2-6hp7 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.