Cyber Resilience

CVE-2024-8925

Php 8.1.0 – 8.1.30

Public PoC
Published
08 October 2024
Modified
03 November 2025
Patch / advisory
View advisory
CVSS Score v3.1 3.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0093 57th percentile
Risk Priority 33 floored blend · peak EPSS

Summary

CVE-2024-8925 is a low-severity HTTP Request/Response Smuggling (CWE-444) vulnerability in Php Php. Its CVSS base score is 3.1 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 43% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SC-7 (Boundary Protection) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

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…

more

control part of the submitted data being able to exclude portion of other data, potentially leading to erroneous application behavior.

CWE(s)
CWE-444

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-17543Same product: Php Php
CVE-2025-1220Same product: Php Php
CVE-2025-14179Same product: Php Php
CVE-2024-9026Same product: Php Php
CVE-2016-3078Same product: Php Php
CVE-2025-1735Same product: Php Php
CVE-2026-6722Same product: Php Php
CVE-2024-11235Same product: Php Php
CVE-2026-7261Same product: Php Php
CVE-2024-8926Same product: Php Php

Affected Assets

php
php
8.1.0 — 8.1.30 · 8.2.0 — 8.2.24 · 8.3.0 — 8.3.12

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V4.1.3
  • V4.2.4
  • V1.5.3
  • V4.1.1

Mitigating Controls (NIST 800-53 r5) AI

SC-7 Boundary Protection partial match

Boundary protection at external interfaces can enforce consistent HTTP request/response parsing rules between intermediaries and endpoints.

SI-10 Information Input Validation partial match

Validating HTTP inputs at the intermediary prevents malformed messages from being interpreted inconsistently downstream.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-01 mostly match
prevents

Configuration management can enforce uniform HTTP parsing rules across intermediaries, directly mitigating inconsistent interpretation.

DE.CM-01 partial match
prevents

Network monitoring can detect smuggling attempts via anomalous HTTP traffic or logs, while eliminating the inconsistency directly aids detection of such events.

PR.IR-01 partial match
prevents

Network protections can enforce consistent HTTP proxy/firewall behavior to block smuggling, and removing the weakness helps prevent unauthorized access via request smuggling.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect HTTP request smuggling vulnerabilities in intermediary components.

A.8.20 Networks security partial match
degrades

Network security controls can enforce consistent HTTP parsing and proxy behavior that mitigates request smuggling.

A.8.21 Security of network services partial match
degrades

Secure network services include hardening proxies and gateways against inconsistent HTTP interpretation.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC practices require threat modeling and testing for HTTP parsing inconsistencies in intermediaries.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate strict HTTP message validation and canonicalization.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include consistent protocol handling and defense-in-depth for proxies.

References