SymfonyFramework / library · Sensiolabs
CVE-2024-51736
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 · uneditedSymphony process is a module for the Symphony PHP framework which executes commands in sub-processes. On Windows, when an executable file named `cmd.exe` is located in the current working directory it will be called by the `Process` class when preparing command arguments, leading to possible hijacking. This issue has been addressed in release versions 5.4.46, 6.4.14, and 7.1.7. Users are advised to upgrade. There are no known workarounds for this vulnerability.
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 confidenceThe Symfony Process component on Windows suffers from an executable hijacking vulnerability. When cmd.exe exists in the current working directory, the Process class uses it instead of the system binary, allowing potential command injection or privilege escalation depending on application context.
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
< 5.4.46>= 6.0.0, < 6.4.14>= 7.0.0, < 7.1.7CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check Symfony Process versionRun `composer show symfony/process` or inspect the version in your composer.lock file under symfony/processAffected if The version is < 5.4.46, or >= 6.0.0 and < 6.4.14, or >= 7.0.0 and < 7.1.7
-
Verify Windows environmentCheck the operating system where your PHP application runs using `php_uname('s')` or checking the PHP_OS constantAffected if The application runs on Windows (the vulnerability only affects Windows environments)
-
Inspect current working directory for cmd.exeList the contents of the current working directory where your Symfony application executes, looking specifically for cmd.exeAffected if cmd.exe is present in the application's current working directory and the Process component is used to execute commands
You are affected if your Symfony Process component version falls within the vulnerable ranges AND your application runs on Windows AND cmd.exe exists in the current working directory where Process executes commands.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.4.466.4.147.1.7
Upgrade Symfony Process to versions 5.4.46, 6.4.14, or 7.1.7 or later. There are no workaround options available for this issue.
Upgrade to Symfony Process 5.4.46 (for 5.x), 6.4.14 (for 6.x), or 7.1.7 (for 7.x) depending on your current major version branch
- Identify your current Symfony version by checking your composer.json or the installed symfony/process package version
- Run 'composer show symfony/process' to confirm the currently installed version
- For Symfony 5.x users: Run 'composer require symfony/process:^5.4.46' to upgrade to the fixed 5.4.46 release
- For Symfony 6.x users: Run 'composer require symfony/process:^6.4.14' to upgrade to the fixed 6.4.14 release
- For Symfony 7.x users: Run 'composer require symfony/process:^7.1.7' to upgrade to the fixed 7.1.7 release
- After upgrade, run 'composer update symfony/process' to install the new version
- Test your application thoroughly, particularly any code that uses the Process component, especially on Windows environments
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Symfony
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,552.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51736 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-51736 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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