PHP
WebUsage: unknown. No public source measures this product yet.
Version split: unknown. No public source for this product.
CVE-2024-8925
Erroneous parsing of multipart form data
No known exploitation. EPSS puts it in the 60th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- PHP Group PHPAffected: ≥ 8.1.*, < 8.1.30Upgrade to: 8.1.30Affected: ≥ 8.2.*, < 8.2.24Upgrade to: 8.2.24Affected: ≥ 8.3.*, < 8.3.12Upgrade to: 8.3.12Stated by: CVE record
- Canonical Ltd. UbuntuAffected: 20.04 LTSUpgrade to: not statedStated by: BDU
- Сообщество свободного программного обеспечения Debian GNU/LinuxAffected: 11Upgrade to: not statedStated by: BDU
- ООО «Ред Софт» РЕД ОСAffected: 7.3Upgrade to: not statedStated by: BDU
- ООО «РусБИТех-Астра» Astra Linux Special EditionAffected: 1.7Upgrade to: not statedStated by: BDU
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In PHP versions 8.1.* before 8.1.30, 8.2.* before 8.2.24, 8.3.* before 8.3.12, erroneous parsing of multipart form data contained in an HTTP POST request could lead to legitimate data not being processed. This could lead to malicious attacker able to control part of the submitted data being able to exclude portion of other data, potentially leading to erroneous application behavior.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
EPSS60th
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.9% chance of exploitation activity in the next 30 days, which ranks it in the 60th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
6 events over 625 days, from the signal feeds we watch.
- OpenVAS check added
- Patch availablerecord updated
- Publishedweakness classified, att&ck mapped
Affected products
Scale
How widely the affected products are used. This is not a count of vulnerable hosts.
Estimate Public sources, each figure dated. How much of it is already patched is not known.
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
Scored 3.1 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
- Privileges Required LowRequires basic user-level privileges
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality NoneNo confidentiality impact
- Integrity LowData modification is possible but limited in scope or consequence
- Availability NoneNo availability impact
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
References in the record
- github.com/php/php-src/security/advisories/GHSA-9pqp-7h25-4f32
- php.net/ChangeLog-8.php
- php.net/ChangeLog-8.php
And 14 more references. See all after sign-in
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for PHP, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI