An issue was discovered in PHP before 5.6.33, 7.0.x before 7.0.27, 7.1.x before 7.1.13, and 7.2.x before 7.2.1.
Noroxi assessment
Priority: Plan (action score 48/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 79.9% (FIRST EPSS); higher than 99.6% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: php5 (Alpine:v3.4) 5.6.36-r0; php5 (Debian:7) 5.4.45-0+deb7u12; php5 (Debian:8) 5.6.33+dfsg-0+deb8u1.
Add it to your regular patch cycle. Upgrade to php5 (Alpine:v3.4) 5.6.36-r0; php5 (Debian:7) 5.4.45-0+deb7u12; php5 (Debian:8) 5.6.33+dfsg-0+deb8u1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An issue was discovered in PHP before 5.6.33, 7.0.x before 7.0.27, 7.1.x before 7.1.13, and 7.2.x before 7.2.1. There is Reflected XSS on the PHAR 404 error page via the URI of a request for a .phar file.
- Published
- Jan 16, 2018
- Updated
- Jun 16, 2026
- EPSS
- 79.9% · 99th percentile
- CWE
- CWE-79
Report tools
Action score
48
Plan
Add it to your regular patch cycle.
- CVSS
- 24 / 40 · 6.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 24 / 30 · 79.9%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| php | php | cpe:2.3:a:php:php |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
Using php? Add it to your stack and be the first to know about CVEs like this one. (PHP)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- php phpup to 5.6.32 inclusive
- php php7.0.0 and later · up to 7.0.26 inclusive
- php phpafter 7.1.0 · up to 7.1.12 inclusive
- php php7.2.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.4 | php5 | before 5.6.36-r0 | 5.6.36-r0 |
| Debian:7 | php5 | before 5.4.45-0+deb7u12 | 5.4.45-0+deb7u12 |
| Debian:8 | php5 | before 5.6.33+dfsg-0+deb8u1 | 5.6.33+dfsg-0+deb8u1 |
| Debian:9 | php7.0 | before 7.0.27-0+deb9u1 | 7.0.27-0+deb9u1 |
| Red Hat:enterprise_linux:7::client | php | before 0:5.4.16-48.el7 | 0:5.4.16-48.el7 |
| Red Hat:enterprise_linux:7::client | php-bcmath | before 0:5.4.16-48.el7 | 0:5.4.16-48.el7 |
| Red Hat:enterprise_linux:7::client | php-cli | before 0:5.4.16-48.el7 | 0:5.4.16-48.el7 |
| Red Hat:enterprise_linux:7::client | php-common | before 0:5.4.16-48.el7 | 0:5.4.16-48.el7 |
| Red Hat:enterprise_linux:7::client | php-dba | before 0:5.4.16-48.el7 | 0:5.4.16-48.el7 |
| Red Hat:enterprise_linux:7::client | php-debuginfo | before 0:5.4.16-48.el7 | 0:5.4.16-48.el7 |
| Red Hat:enterprise_linux:7::client | php-devel | before 0:5.4.16-48.el7 | 0:5.4.16-48.el7 |
| Red Hat:enterprise_linux:7::client | php-embedded | before 0:5.4.16-48.el7 | 0:5.4.16-48.el7 |
| Red Hat:enterprise_linux:7::client | php-enchant | before 0:5.4.16-48.el7 | 0:5.4.16-48.el7 |
| Red Hat:enterprise_linux:7::client | php-fpm | before 0:5.4.16-48.el7 | 0:5.4.16-48.el7 |
| Red Hat:enterprise_linux:7::client | php-gd | before 0:5.4.16-48.el7 | 0:5.4.16-48.el7 |
| Red Hat:enterprise_linux:7::client | php-intl | before 0:5.4.16-48.el7 | 0:5.4.16-48.el7 |
| Red Hat:enterprise_linux:7::client | php-ldap | before 0:5.4.16-48.el7 | 0:5.4.16-48.el7 |
| Red Hat:enterprise_linux:7::client | php-mbstring | before 0:5.4.16-48.el7 | 0:5.4.16-48.el7 |
| Red Hat:enterprise_linux:7::client | php-mysql | before 0:5.4.16-48.el7 | 0:5.4.16-48.el7 |
| Red Hat:enterprise_linux:7::client | php-mysqlnd | before 0:5.4.16-48.el7 | 0:5.4.16-48.el7 |
| Red Hat:enterprise_linux:7::client | php-odbc | before 0:5.4.16-48.el7 | 0:5.4.16-48.el7 |
| Red Hat:enterprise_linux:7::client | php-pdo | before 0:5.4.16-48.el7 | 0:5.4.16-48.el7 |
| Red Hat:enterprise_linux:7::client | php-pgsql | before 0:5.4.16-48.el7 | 0:5.4.16-48.el7 |
| Red Hat:enterprise_linux:7::client | php-process | before 0:5.4.16-48.el7 | 0:5.4.16-48.el7 |
+39
Same product
php: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-4577Argument Injection in PHP-CGIKEV99Now
- CVE-2019-11043Underflow in PHP-FPM can lead to RCEKEV99Now
- CVE-2012-1823sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not properly handle queKEV99Now
- CVE-2018-7584In PHP through 5.6.33, 7.0.x before 7.0.28, 7.1.x through 7.1.14, and 7.2.x through 7.2.2, there is a stack-based buffer under-read while pa65This week
- CVE-2018-19518University of Washington IMAP Toolkit 2007f on UNIX, as used in imap_open() in PHP and other products, launches an rsh command (by means of 59Plan
- CVE-2016-3078Multiple integer overflows in php_zip.c in the zip extension in PHP before 7.0.6 allow remote attackers to cause a denial of service (heap-b56Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:php5 | 5.6.36-r0 · Alpine:v3.4 | Package registry (OSV) |
| debian:php5 | 5.4.45-0+deb7u12 · Debian:7 | Package registry (OSV) |
| debian:php7.0 | 7.0.27-0+deb9u1 · Debian:9 | Package registry (OSV) |
| red hat:rh-php71-php | 0:7.1.30-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-php71-php-bcmath | 0:7.1.30-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-php71-php-cli | 0:7.1.30-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-php71-php-common | 0:7.1.30-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-php71-php-dba | 0:7.1.30-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-php71-php-dbg | 0:7.1.30-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-php71-php-debuginfo | 0:7.1.30-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-php71-php-devel | 0:7.1.30-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-php71-php-embedded | 0:7.1.30-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-php71-php-enchant | 0:7.1.30-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-php71-php-fpm | 0:7.1.30-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-php71-php-gd | 0:7.1.30-1.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| suse:php5 | 5.5.14-109.17.1 · SUSE:Linux Enterprise Module for Web and Scripting 12 | Package registry (OSV) |
| suse:php53 | 5.3.17-112.20.1 · SUSE:Linux Enterprise Software Development Kit 11 SP4 | Package registry (OSV) |
| suse:php7 | 7.0.7-50.26.1 · SUSE:Linux Enterprise Module for Web and Scripting 12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
nvd-primary
Root cause
User content is inserted into the page as HTML. The browser interprets the content as code rather than data.
The bug in code
The whole CWE-79 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
commentEl.innerHTML = comment.body;Fixed
commentEl.textContent = comment.body;Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (12 more)Show less
- php.net/ChangeLog-7.php
- www.securityfocus.com/bid/102742
- www.securityfocus.com/bid/104020
- www.securitytracker.com/id/1040363
- access.redhat.com/errata/RHSA-2018:1296
- access.redhat.com/errata/RHSA-2019:2519
- bugs.php.net/bug.php?id=74782
- lists.debian.org/debian-lts-announce/2018/01/msg00025.html
- usn.ubuntu.com/3566-1/
- usn.ubuntu.com/3600-1/
- usn.ubuntu.com/3600-2/
- www.oracle.com/security-alerts/cpuapr2020.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.