PHPApplication
CVE-2025-1736
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 · uneditedIn PHP from 8.1.* before 8.1.32, from 8.2.* before 8.2.28, from 8.3.* before 8.3.19, from 8.4.* before 8.4.5, when user-supplied headers are sent, the insufficient validation of the end-of-line characters may prevent certain headers from being sent or lead to certain headers be misinterpreted.
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 confidencePHP versions prior to 8.1.32, 8.2.28, 8.3.19, and 8.4.5 contain insufficient validation of end-of-line characters in user-supplied HTTP headers. This flaw can prevent certain headers from being sent or cause headers to be misinterpreted, potentially enabling HTTP response splitting or header injection attacks.
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
PHPApplication
>= 8.1.0, < 8.1.32>= 8.2.0, < 8.2.28>= 8.3.0, < 8.3.19>= 8.4.0, < 8.4.5= 9CVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Determine installed PHP versionRun 'php -v' on the command line or use phpinfo() in a script to retrieve the PHP version numberAffected if The version shown is 8.1.x less than 8.1.32, 8.2.x less than 8.2.28, 8.3.x less than 8.3.19, or 8.4.x less than 8.4.5
-
Confirm PHP is processing HTTP requestsCheck if PHP is running as an Apache module, FPM, or behind a web server like Nginx or is being used to handle incoming HTTP requestsAffected if PHP is actively processing HTTP headers from client requests, as the vulnerability involves validation of user-supplied HTTP header data
-
Identify header handling codeReview application code for uses of header(), setcookie(), or other functions that send HTTP headers, especially those that incorporate user inputAffected if The application sends custom headers using values derived from user input, which could contain malicious EOL characters
-
Check for NetApp Ontap PHP usageIf PHP is embedded in NetApp Ontap 9, verify the PHP component version through the system documentation or ontap CLIAffected if The system runs NetApp Ontap version 9 with an embedded PHP version matching the affected ranges above
You are affected if your installed PHP version falls within any of the vulnerable ranges (8.1.0-8.1.31, 8.2.0-8.2.27, 8.3.0-8.3.18, or 8.4.0-8.4.4) and your PHP installation processes HTTP headers from untrusted sources.
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 · scoped8.1.328.2.288.3.19
Upgrade PHP to version 8.1.32, 8.2.28, 8.3.19, 8.4.5 or later to receive the patch for proper end-of-line character validation in headers.
PHP 8.1.32, 8.2.28, 8.3.19, or 8.4.5 (whichever branch you are on); NetApp ONTAP 9.x to patched version per vendor advisory
- Identify the currently installed PHP version using 'php -v' or 'php --version'
- For Debian-based systems: Run 'apt update' then 'apt install php' to upgrade to the latest available version in your repository
- For RHEL/CentOS systems: Run 'yum update php' or 'dnf update php'
- For systems using Ondřej Surý PPA (Ubuntu/Debian): Run 'apt update' then 'apt install php8.1, php8.2, php8.3, or php8.4 depending on your desired version
- Alternatively, download the specific fixed version directly from php.net/downloads.php
- After upgrade, verify the installed version matches or exceeds the fixed release (8.1.32, 8.2.28, 8.3.19, or 8.4.5) using 'php -v'
- Test your applications to ensure they function correctly with the new PHP version
- For NetApp ONTAP 9: Apply the corresponding security patch from security.netapp.com
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in PHP
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing8.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 $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1736 — 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-2025-1736 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