CVE-2026-47212

Symfony: Twilio Notifier Webhook Parser Never Verifies the X-Twilio-Signature HMAC: Unauthenticated Webhook Event Injection

MEDIUM

5.3

CVSS Score

Published: July 14, 2026 at 07:00 PM UTC

Updated: July 15, 2026 at 03:14 PM UTC

3 products affected across 2 vendorsSymfonySymfonyTwilio Notifier

Using symfony by symfony?

Get instant alerts when new vulnerabilities affect symfony - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.3

Exploit prediction

EPSS 2%

SSVC

No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Symfony · Sensiolabsdrupal

95%

6.4.0 ≤ v < 6.4.407.0.0 ≤ v < 7.4.128.0.0 ≤ v < 8.0.12

Affected range stops below 6.4.40, so it looks safe — our inference, not a vendor statement

Affected range stops below 7.4.12, so it looks safe — our inference, not a vendor statement

Affected range stops below 8.0.12, so it looks safe — our inference, not a vendor statement

Symfony · Symfonycomposer

60%

v < 6.4.40v < 7.4.12v < 8.0.12

Affected range stops below 6.4.40, so it looks safe — our inference, not a vendor statement

Affected range stops below 7.4.12, so it looks safe — our inference, not a vendor statement

Affected range stops below 8.0.12, so it looks safe — our inference, not a vendor statement

Twilio Notifier · Symfony

60%

v < 6.4.40v < 7.4.12v < 8.0.12

Affected range stops below 6.4.40, so it looks safe — our inference, not a vendor statement

Affected range stops below 7.4.12, so it looks safe — our inference, not a vendor statement

Affected range stops below 8.0.12, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (5)

x_refsource_CONFIRMPatchVendor Advisory

Source: cverecord

https://github.com/symfony/symfony/security/advisories/GHSA-55rj-x2vc-4whq

x_refsource_MISCPatch

Source: cverecord

https://github.com/symfony/symfony/commit/8545fb2af6c07dfb5ef0fc8d9bccf86db2c94356

x_refsource_MISCProductRelease Notes

Source: cverecord

https://github.com/symfony/symfony/releases/tag/v6.4.40

x_refsource_MISCProductRelease Notes

Source: cverecord

https://github.com/symfony/symfony/releases/tag/v7.4.12

x_refsource_MISCProductRelease Notes

Source: cverecord

https://github.com/symfony/symfony/releases/tag/v8.0.12

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.3MEDIUM[email protected]

Attack Vector: NETWORK
Complexity: LOW
Privileges: NONE
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: NONE
Integrity: LOW
Availability: NONE

Vector?

Quick Info

StatusANALYZED

CWE

CWE-306CWE-347

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card