dbcve.org
SymfonyFramework / library · Sensiolabs

CVE-2026-45072

MEDIUM · 5.4 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 →
58/100
Remediation priority · Elevated
Remotely reachable 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. From 6.4.24 until 6.4.40, 7.4.12, and 8.0.12, the development profiler file_excerpt Twig filter escapes PHP files through highlight_string() but interpolates lines from non-PHP files directly into <code> elements, allowing stored XSS against a developer who opens an attacker-written file such as var/log/dev.log in the profiler. 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 file_excerpt Twig filter in Symfony's development profiler escapes PHP files properly via highlight_string() but fails to escape content from non-PHP files, directly interpolating attacker-controlled content into HTML <code> elements. An attacker can inject malicious JavaScript into files like var/log/dev.log that executes when a developer views the file in the profiler.

MitigationUpgrade Symfony to versions 6.4.40, 7.4.12, 8.0.12 or later. Until then, avoid opening untrusted or user-controlled log files in the development profiler.

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.24, < 6.4.40>= 7.2.9, < 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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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. Determine your installed Symfony version
    Check composer.json for the 'symfony/framework-bundle' version, or run 'composer show symfony/framework-bundle | grep version', or inspect vendor/symfony/framework-bundle/VERSION
    Affected if The version falls within 6.4.24 to 6.4.39, 7.2.9 to 7.4.11, or 8.0.0 to 8.0.11
  2. Verify development mode is enabled
    Check your environment: look for APP_ENV=dev in your .env file, environment variables, or server configuration
    Affected if APP_ENV is set to 'dev' (the profiler is only active in development mode)
  3. Confirm the debug toolbar and profiler are accessible
    Check that your application has the symfony/profiler-bundle installed (composer show symfony/profiler-bundle) and that the web debug toolbar appears when loading pages
    Affected if The profiler bundle is installed and visible in the development environment
  4. Identify log files that may have been viewed in the profiler
    Review var/log/dev.log or any custom log files you have viewed through the profiler's file viewer feature
    Affected if You have viewed non-PHP files (such as log files) through the Symfony profiler's file viewer in a vulnerable version

You are affected if you run a vulnerable Symfony version (6.4.24-6.4.39, 7.2.9-7.4.11, or 8.0.0-8.0.11), have the development profiler enabled, and have viewed non-PHP files through the profiler's file viewer.

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 versions 6.4.40, 7.4.12, 8.0.12 or later. Until then, avoid opening untrusted or user-controlled log files in the development profiler.

Recommended fix High confidence

Upgrade to Symfony 6.4.40 (for 6.4.x users), 7.4.12 (for 7.x users), or 8.0.12 (for 8.x users)

  1. 1. Identify the current Symfony version by checking composer.json or running `composer show symfony/framework-bundle version`
  2. 2. Update the Symfony version constraint in composer.json to one of: 6.4.40, 7.4.12, or 8.0.12 (depending on your major version)
  3. 3. Run `composer update symfony/framework-bundle --with-all-dependencies` or `composer update` to apply the upgrade
  4. 4. Test the application to ensure the upgrade does not break existing functionality
  5. 5. Verify the profiler file_excerpt function now properly escapes non-PHP file content
Caveat Minor/patch upgrades typically have low breaking change risk, but test thoroughly as with any upgrade

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

Fix this in Symfony Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45072 — 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-45072 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