cve.bz

CVE-2017-9841 PHPUnit Command Injection Vulnerability

9.8 criticalKEVExploitEPSS >99.9%Fix available

Critical (9.8) in PHPUnit PHPUnit. In CISA KEV since 2022-02-15. EPSS >99.9% estimated probability of exploitation activity in the next 30 days. Fixed in phpunit/phpunit 4.8.28, 5.6.3.

On this page
Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP code via HTTP POST data beginning with a "<?php " substring, as demonstrated by an attack on a site with an exposed /vendor folder, i.e., external access to the /vendor/phpunit/phpunit/src/Util/PHP/eval-stdin.php URI.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
>99.9% (unchanged from >99.9% a week ago; >99.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2022-02-15, due 2022-08-15
CISA's assessment (SSVC)
Exploitation: active · Automatable: yes · Technical impact: total, assessed 2025-02-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-94 Improper Control of Generation of Code (Code Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2017-9841 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-9841?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-9841?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-9841 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
phpunit_project:phpunitthrough 4.8.27
phpunit_project:phpunitfrom 5.0.0 before 5.6.3
oracle:communications_diameter_signaling_routerfrom 8.0.0 through 8.5.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-r7c9-c69m-rph8Packagistphpunit/phpunit>=4.8.19 <4.8.284.8.28
GHSA-r7c9-c69m-rph8Packagistphpunit/phpunit>=5.0.10 <5.6.35.6.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14phpunit5.4.6-2DEBIAN-CVE-2017-9841
UbuntuPro:16.04:LTSphpunit5.1.3-1+ubuntu3+esm1UBUNTU-CVE-2017-9841 USN-7171-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Public exploits

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
  • CAPEC-242 Code Injection Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON