CVE-2015-10133

HIGHNVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2025-07-19. NVD baseline CVSS 7.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
7.2EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • Public exploit code is available (Metasploit, public exploit)
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.2Exploit: Metasploit · public exploitExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The Subscribe to Comments for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 2.1.2 via the Path to header value. This allows authenticated attackers, with administrative privileges and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included. This same function can also be used to execute arbitrary PHP code.

CVSS v3
7.2
EG Score
7.2(medium)
EG Risk
58(Track)
EG Risk 58/100SSVC: Track

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
Severity72% × 45%
Exploitation65% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
70%
KEV
Not listed

Published

July 19, 2025

Last Modified

December 23, 2025

References (5)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-26 14:50 UTCEPSS rescore
  2. 2026-07-24 14:13 UTCEPSS rescore
  3. 2026-07-23 14:14 UTCEPSS rescore
  4. 2026-07-23 01:16 UTCEG score recompute
  5. 2026-07-23 00:19 UTCEG score recompute
  6. 2026-07-22 21:57 UTCEG score recompute
  7. 2026-07-22 14:04 UTCEPSS rescore
  8. 2026-07-21 15:21 UTCEPSS rescore
  9. 2026-07-21 15:21 UTCEPSS rescore
  10. 2026-07-20 17:03 UTCEPSS rescore
  11. 2026-07-19 14:27 UTCEPSS rescore
  12. 2026-07-19 14:27 UTCEPSS rescore
  13. 2026-07-19 02:26 UTCEPSS rescore
  14. 2026-07-19 02:26 UTCEPSS rescore
  15. 2026-07-18 10:00 UTCEPSS rescore
  16. 2026-07-16 16:59 UTCEPSS rescore
  17. 2026-07-16 16:59 UTCEPSS rescore
  18. 2026-07-15 16:54 UTCEPSS rescore
  19. 2026-07-15 16:54 UTCEPSS rescore
  20. 2026-07-15 01:56 UTCEPSS rescore
  21. 2026-07-13 22:26 UTCEPSS rescore
  22. 2026-07-12 05:42 UTCEPSS rescore
  23. 2026-07-11 08:23 UTCEPSS rescore
  24. 2026-07-09 19:05 UTCEPSS rescore
  25. 2026-07-08 15:10 UTCEPSS rescore
Show 51 more
  1. 2026-07-07 13:42 UTCEPSS rescore
  2. 2026-07-06 16:24 UTCEPSS rescore
  3. 2026-07-06 02:20 UTCEPSS rescore
  4. 2026-07-05 02:26 UTCEPSS rescore
  5. 2026-07-04 06:27 UTCEPSS rescore
  6. 2026-07-02 15:21 UTCEPSS rescore
  7. 2026-07-01 15:02 UTCEPSS rescore
  8. 2026-07-01 15:02 UTCEPSS rescore
  9. 2026-06-30 23:19 UTCEPSS rescore
  10. 2026-06-30 23:19 UTCEPSS rescore
  11. 2026-06-28 14:03 UTCEPSS rescore
  12. 2026-06-28 04:53 UTCEPSS rescore
  13. 2026-06-27 03:05 UTCEPSS rescore
  14. 2026-06-25 13:47 UTCEPSS rescore
  15. 2026-06-25 13:47 UTCEPSS rescore
  16. 2026-06-24 14:02 UTCEPSS rescore
  17. 2026-06-24 14:02 UTCEPSS rescore
  18. 2026-06-23 21:30 UTCEPSS rescore
  19. 2026-06-22 14:23 UTCEPSS rescore
  20. 2026-06-22 14:22 UTCEPSS rescore
  21. 2026-06-21 14:54 UTCEPSS rescore
  22. 2026-06-21 01:57 UTCEPSS rescore
  23. 2026-06-21 01:57 UTCEPSS rescore
  24. 2026-06-19 19:23 UTCEPSS rescore
  25. 2026-06-19 19:23 UTCEPSS rescore
  26. 2026-06-18 17:50 UTCEPSS rescore
  27. 2026-06-18 17:49 UTCEPSS rescore
  28. 2026-06-17 17:49 UTCEPSS rescore
  29. 2026-06-16 17:50 UTCEPSS rescore
  30. 2026-06-16 17:49 UTCEPSS rescore
  31. 2026-06-15 17:45 UTCEPSS rescore
  32. 2026-06-13 22:57 UTCEPSS rescore
  33. 2026-06-12 23:09 UTCEPSS rescore
  34. 2026-06-11 13:57 UTCEPSS rescore
  35. 2026-06-10 22:15 UTCEPSS rescore
  36. 2026-06-08 14:14 UTCEPSS rescore
  37. 2026-06-07 15:22 UTCEPSS rescore
  38. 2026-06-06 13:45 UTCEPSS rescore
  39. 2026-06-05 22:44 UTCEPSS rescore
  40. 2026-06-05 06:08 UTCEPSS rescore
  41. 2026-06-05 06:08 UTCEPSS rescore
  42. 2026-06-04 13:10 UTCEPSS rescore
  43. 2026-06-04 13:09 UTCEPSS rescore
  44. 2026-06-02 20:10 UTCEPSS rescore
  45. 2026-06-02 20:10 UTCEPSS rescore
  46. 2026-06-01 13:49 UTCEPSS rescore
  47. 2026-06-01 13:49 UTCEPSS rescore
  48. 2026-05-31 00:14 UTCEPSS rescore
  49. 2026-05-30 01:44 UTCEG score recompute
  50. 2026-05-30 01:44 UTCGHSA enrichment
  51. 2026-05-29 13:41 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Metasploit module). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Metasploitauxiliary/scanner/http/wp_subscribe_comments_file_read✓ verified
    First seen Jan 1, 2015

    WordPress Subscribe Comments File Read Vulnerability

    Open source ↗

Frequently asked(5)

What is CVE-2015-10133?
CVE-2015-10133 is a high vulnerability published on July 19, 2025. The Subscribe to Comments for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 2.1.2 via the Path to header value. This allows authenticated attackers, with administrative privileges and above, to include and execute arbitrary files on the server, allowing the…
When was CVE-2015-10133 disclosed?
CVE-2015-10133 was first published in the National Vulnerability Database on July 19, 2025, with the most recent update on December 23, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2015-10133 actively exploited?
CVE-2015-10133 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 29.6% of all scored CVEs.
What is the CVSS score of CVE-2015-10133?
CVE-2015-10133 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2015-10133?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-10133, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2015-10133

Explore →

Is Your Infrastructure Affected by CVE-2015-10133?

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

Start Free Scan →Browse All CVEs