dbcve.org
SymfonyFramework / library · Sensiolabs

CVE-2026-47212

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 6.4.40 / 7.4.12 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Prior to 6.4.40, 7.4.12, and 8.0.12, TwilioRequestParser::doParse() received the configured webhook secret but ignored the X-Twilio-Signature HMAC header, allowing unauthenticated POST requests to inject forged Twilio status payloads. This issue is fixed in versions 6.4.40, 7.4.12, and 8.0.12.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The TwilioRequestParser::doParse() method in Symfony receives the configured webhook secret but fails to validate the X-Twilio-Signature HMAC header, allowing attackers to send forged Twilio status callback payloads without authentication.

MitigationUpgrade Symfony to version 6.4.40, 7.4.12, or 8.0.12 to include the HMAC signature validation fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SymfonyFramework / library
Affected:>= 6.4.0, < 6.4.40>= 7.0.0, < 7.4.12>= 8.0.0, < 8.0.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Symfony version
    Run `composer show symfony/framework-bundle 2>/dev/null | grep version` or check your composer.lock file for the symfony/framework-bundle package version
    Affected if The version is >= 6.4.0 and < 6.4.40, OR >= 7.0.0 and < 7.4.12, OR >= 8.0.0 and < 8.0.12
  2. Locate Twilio webhook configuration
    Search your Symfony configuration files (config/packages/*.yaml, config/services.yaml) for 'twilio', 'TwilioWebhook', or 'X-Twilio-Signature' keywords
    Affected if Twilio webhook handling is configured and the application uses Symfony's TwilioRequestParser class
  3. Verify webhook secret is set
    Check your configuration for a parameter such as 'twilio.webhook.secret', 'twilio_secret', or similar that provides the secret used for HMAC validation of the X-Twilio-Signature header
    Affected if A webhook secret is configured but the HMAC validation is not being performed by the vulnerable TwilioRequestParser::doParse() method
  4. Confirm request parser usage
    Search your codebase for references to TwilioRequestParser or the 'twilio' request parser type in your security or routing configuration
    Affected if The application routes Twilio status callbacks through Symfony's TwilioRequestParser without the fix applied

You are affected if you run a vulnerable Symfony version (6.4.0-6.4.39, 7.0.0-7.4.11, or 8.0.0-8.0.11) AND have Twilio webhook endpoints configured that rely on the TwilioRequestParser for authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.4.40 / 7.4.12 / 8.0.12 or later
Fixed in 6.4.407.4.128.0.12
Interim mitigation

Upgrade Symfony to version 6.4.40, 7.4.12, or 8.0.12 to include the HMAC signature validation fix.

Recommended fix High confidence

Symfony 6.4.40, 7.4.12, or 8.0.12 (depending on your major version branch)

  1. Identify your current Symfony version from your composer.json or lock file
  2. Run 'composer require symfony/framework-bundle:^6.4.40' for Symfony 6.4.x, 'composer require symfony/framework-bundle:^7.4.12' for Symfony 7.x, or 'composer require symfony/framework-bundle:^8.0.12' for Symfony 8.x
  3. Run 'composer update symfony/framework-bundle --with-all-dependencies' to apply the security fix
  4. Verify the installed version matches the minimum fixed release using 'composer show symfony/framework-bundle | grep version'
  5. Clear your application cache after upgrading (e.g., 'php bin/console cache:clear')
Caveat Minor version upgrades in Symfony typically have minimal breaking changes; review the Symfony UPGRADE guide for your version for any deprecation notices

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Symfony Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47212 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47212 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data