CVE-2017-9841

CRITICALNVD 9.89.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-02-15), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, NVD CVSS v3
Trending — 3 sources updated this weekExploited in the wild
9.8EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low mission impact
CISA-KEV: ExploitedEPSS PROB: >99.9%CVSS: 9.8Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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 "

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low mission impact; Act at medium or high.
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.
EPSS PROB
>99.9%
EPSS %ILE
99th
KEV
⚠ Exploited

SSVC (CISA's decision table, applied by EchelonGraph)Attend at low mission impact; Act at medium or high.

A fix is available. Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.

In CISA KEV yes (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2017-9841

Published

June 27, 2017

Last Modified

June 17, 2026

Advisory Details (6)

Auto-updated Oct 12, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: github_commit, github_pr.
Web page

CVE-2017-9841 - PSIRT.COM

http://www.securityfocus.com/bid/101798
Web page

CVE-2017-9841 RCE vulnerability in phpunit

http://web.archive.org/web/20170701212357/http://phpunit.vulnbusters.com/
Web page

PHPUnit: Remote code execution (GLSA 201711-15) — Gentoo security

https://security.gentoo.org/glsa/201711-15
GitHub pull request

Fix insulated tests with phpdbg

Fix merged in sebastianbergmann/phpunit PR #1956 on 2015-11-17 — awaiting tagged release

https://github.com/sebastianbergmann/phpunit/pull/1956
GitHub commit Patch Available

commit 284a69fb88a2 (sebastianbergmann/phpunit)

Patch available: sebastianbergmann/phpunit 13.2.4 (contains commit 284a69fb88a2)

https://github.com/sebastianbergmann/phpunit/commit/284a69fb88a2d0845d23f42974a583d8f59bf5a5
Web page
http://www.securitytracker.com/id/1039812

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuphpunit (5.1.3-1+ubuntu3+esm1) @ xenial2026-10-13ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
phpunit—
  • every version up to 5.4.6-2: fixed in 5.4.6-2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
phpunit—
  • every version up to 5.4.6-2: fixed in 5.4.6-2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
phpunit—
  • every version up to 5.4.6-2: fixed in 5.4.6-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
phpunit—
  • every version up to 5.4.6-2: fixed in 5.4.6-2
—
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
phpunit/phpunit5.0.10 ... 5.6.2 (48 versions)
  • 4.8.19 up to 4.8.28: fixed in 4.8.28
  • 5.0.10 up to 5.6.3: fixed in 5.6.3
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 28× in last 7d / 168× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 743 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 644 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 18:23 UTCEG score recompute
  2. 2026-10-14 16:27 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  3. 2026-10-13 17:25 UTCEG score recompute
  4. 2026-10-13 17:25 UTCVendor advisory
  5. 2026-10-12 16:28 UTCEG score recompute
  6. 2026-10-12 05:05 UTCVendor advisory
  7. 2026-10-12 01:13 UTCVendor advisory
  8. 2026-10-11 21:22 UTCEG score recompute
  9. 2026-10-11 21:22 UTCVendor advisory
  10. 2026-10-11 17:31 UTCEG score recompute
  11. 2026-10-11 13:39 UTCEG score recompute
  12. 2026-10-11 13:39 UTCVendor advisory
  13. 2026-10-11 09:44 UTCVendor advisory
  14. 2026-10-11 05:54 UTCVendor advisory
  15. 2026-10-10 14:22 UTCVendor advisory
  16. 2026-10-10 10:32 UTCVendor advisory
  17. 2026-10-10 06:41 UTCVendor advisory
  18. 2026-10-10 02:51 UTCVendor advisory
  19. 2026-10-09 23:02 UTCVendor advisory
  20. 2026-10-09 19:13 UTCVendor advisory
  21. 2026-10-09 15:23 UTCVendor advisory
  22. 2026-10-09 11:33 UTCVendor advisory
  23. 2026-10-09 07:43 UTCVendor advisory
  24. 2026-10-09 03:53 UTCVendor advisory
  25. 2026-10-09 00:03 UTCVendor advisory
Show 74 more
  1. 2026-10-08 12:30 UTCVendor advisory
  2. 2026-10-08 08:41 UTCVendor advisory
  3. 2026-10-08 04:51 UTCVendor advisory
  4. 2026-10-07 17:21 UTCVendor advisory
  5. 2026-10-07 09:39 UTCVendor advisory
  6. 2026-10-07 05:50 UTCVendor advisory
  7. 2026-10-07 02:00 UTCVendor advisory
  8. 2026-10-06 22:10 UTCVendor advisory
  9. 2026-10-06 18:20 UTCEG score recompute
  10. 2026-10-06 18:20 UTCVendor advisory
  11. 2026-10-06 15:12 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  12. 2026-10-06 14:31 UTCVendor advisory
  13. 2026-10-06 10:41 UTCVendor advisory
  14. 2026-10-06 02:59 UTCVendor advisory
  15. 2026-10-05 19:16 UTCVendor advisory
  16. 2026-10-05 15:24 UTCVendor advisory
  17. 2026-10-05 11:33 UTCVendor advisory
  18. 2026-10-05 07:44 UTCVendor advisory
  19. 2026-10-05 03:54 UTCVendor advisory
  20. 2026-10-05 00:01 UTCVendor advisory
  21. 2026-10-04 16:20 UTCVendor advisory
  22. 2026-10-04 12:29 UTCVendor advisory
  23. 2026-10-04 08:39 UTCVendor advisory
  24. 2026-10-04 04:48 UTCVendor advisory
  25. 2026-10-04 00:59 UTCVendor advisory
  26. 2026-10-03 21:09 UTCVendor advisory
  27. 2026-10-03 17:19 UTCVendor advisory
  28. 2026-10-03 13:30 UTCVendor advisory
  29. 2026-10-03 05:49 UTCVendor advisory
  30. 2026-10-03 01:59 UTCVendor advisory
  31. 2026-10-02 22:09 UTCVendor advisory
  32. 2026-10-02 18:18 UTCVendor advisory
  33. 2026-10-02 06:40 UTCVendor advisory
  34. 2026-10-01 22:56 UTCVendor advisory
  35. 2026-10-01 19:07 UTCVendor advisory
  36. 2026-10-01 15:16 UTCVendor advisory
  37. 2026-10-01 11:26 UTCVendor advisory
  38. 2026-10-01 07:37 UTCVendor advisory
  39. 2026-10-01 03:47 UTCVendor advisory
  40. 2026-09-30 23:58 UTCVendor advisory
  41. 2026-09-30 16:16 UTCVendor advisory
  42. 2026-09-30 08:36 UTCVendor advisory
  43. 2026-09-30 04:46 UTCVendor advisory
  44. 2026-09-30 00:56 UTCVendor advisory
  45. 2026-09-29 21:07 UTCVendor advisory
  46. 2026-09-29 17:13 UTCVendor advisory
  47. 2026-09-29 09:30 UTCVendor advisory
  48. 2026-09-29 05:41 UTCVendor advisory
  49. 2026-09-29 01:51 UTCVendor advisory
  50. 2026-09-28 22:01 UTCEG score recompute
  51. 2026-09-28 22:01 UTCVendor advisory
  52. 2026-09-28 14:18 UTCVendor advisory
  53. 2026-09-28 10:28 UTCVendor advisory
  54. 2026-09-28 06:38 UTCVendor advisory
  55. 2026-09-28 02:48 UTCVendor advisory
  56. 2026-09-27 22:59 UTCVendor advisory
  57. 2026-09-27 21:51 UTCCISA KEV update
  58. 2026-09-27 19:09 UTCVendor advisory
  59. 2026-09-27 15:19 UTCVendor advisory
  60. 2026-09-27 11:27 UTCVendor advisory
  61. 2026-09-27 07:37 UTCVendor advisory
  62. 2026-09-27 03:47 UTCVendor advisory
  63. 2026-09-26 23:56 UTCVendor advisory
  64. 2026-09-26 20:06 UTCVendor advisory
  65. 2026-09-26 16:16 UTCVendor advisory
  66. 2026-09-26 12:24 UTCVendor advisory
  67. 2026-09-26 08:34 UTCVendor advisory
  68. 2026-09-26 04:44 UTCVendor advisory
  69. 2026-09-26 00:52 UTCVendor advisory
  70. 2026-09-25 21:02 UTCVendor advisory
  71. 2026-09-25 19:35 UTCCISA KEV update
  72. 2026-09-25 17:12 UTCVendor advisory
  73. 2026-09-25 14:55 UTCCISA KEV update
  74. 2026-09-25 13:22 UTCVendor advisory

Publicly available exploits

(11 references, 10 shown)

Public exploit code is referenced for this CVE (1 Exploit-DB entry, 7 GitHub PoCs), as are 1 Nuclei detection template, 2 GitHub checker repositories. A detection template checks whether a system is affected; it is not necessarily exploit code. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • GitHub checkerdrcrypterdotru/PHPUnit-GoScan
    Published Aug 30, 2025

    PHPUnit CVE-2017-9841 Scanner in Go clean and fire.

    Open source ↗
  • GitHub PoCChocapikk/CVE-2017-9841
    Published Aug 27, 2023

    PHPUnit RCE

    Open source ↗
  • GitHub checkerMrG3P5/CVE-2017-9841
    Published Mar 13, 2023

    A Tool for scanning CVE-2017-9841 with multithread

    Open source ↗
  • GitHub PoCMadExploits/PHPunit-Exploit
    Published Dec 7, 2022

    PHPunit Checker CVE-2017-9841 By MrMad

    Open source ↗
  • GitHub PoCp1ckzi/CVE-2017-9841
    Published Apr 9, 2022

    phpunit-shell | CVE_2017-9841

    Open source ↗
  • GitHub PoCakr3ch/CVE-2017-9841
    Published Mar 20, 2022

    RCE exploit for PHP Unit 5.6.2

    Open source ↗
  • Exploit-DBEDB-50702
    Published Feb 2, 2022

    PHP Unit 4.8.28 - Remote Code Execution (RCE) (Unauthenticated)

    Open source ↗
  • GitHub PoCincogbyte/laravel-phpunit-rce-masscaner
    Published Jul 4, 2021

    Masscanner for Laravel phpunit RCE CVE-2017-9841

    Open source ↗
  • GitHub PoCludy-dev/PHPUnit_eval-stdin_RCE
    Published Sep 14, 2020

    (CVE-2017-9841) PHPUnit_eval-stdin_php Remote Code Execution

    Open source ↗
  • Nucleihttp/cves/2017/CVE-2017-9841.yaml
    Published Aug 7, 2020

    PHPUnit - Remote Code Execution

    Open source ↗

Related CVEs(same product + same CWE)

Same product

2 shown

Debian:11:phpunit · Packagist:phpunit/phpunit

Frequently asked(6)

What is CVE-2017-9841?
CVE-2017-9841 is a critical-severity vulnerability; its CVE record was published on June 27, 2017. 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…
When was CVE-2017-9841 made public?
CVE-2017-9841 was made public on June 27, 2017: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on June 27, 2017. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2017-9841 actively exploited?
Yes. CISA added CVE-2017-9841 to the Known Exploited Vulnerabilities catalog on February 15, 2022, affecting PHPUnit PHPUnit. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2017-9841?
CVE-2017-9841 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2017-9841?
CVE-2017-9841 affects PHPUnit PHPUnit. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2017-9841?
A fix for CVE-2017-9841 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-9841

Explore →

Is Your Infrastructure Affected by CVE-2017-9841?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs