CVE-2026-12115

MEDIUMPre-NVD 6.66.6
EchelonGraph scoreMEDIUM confidence

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

Score 6.6 from GitHub Security Advisory published 2026-06-17. A secondary CVSS source baseline 6.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
6.6EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.6Exploit: None knownExposed services: Not assessed

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

The Counter Box – Add Countdowns, Timers & Dynamic Counters to WordPress plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 2.0.13 via deserialization of untrusted input . This makes it possible for authenticated attackers, with administrator-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present. Deserialization is triggered automatically upon the post-import redirect that renders the list table, and again when any item is opened for editing, requiring no additional navigation beyond the import action itself.

CVSS v3
6.6
EG Score
6.6MEDIUMmedium confidence
EG Risk
30
EG Risk 30/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)
Severity66% × 45%
The EG Score, 6.6 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

Published

June 17, 2026

Last Modified

June 17, 2026

References (6)

Vendor Advisories for CVE-2026-12115(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 24× 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 100 of 196 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. None are among the latest 100 rows. The 96 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-12115?
CVE-2026-12115 is a medium-severity vulnerability; its CVE record was published on June 17, 2026. The Counter Box – Add Countdowns, Timers & Dynamic Counters to WordPress plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 2.0.13 via deserialization of untrusted input . This makes it possible for authenticated attackers, with administrator-level…
When was the CVE record for CVE-2026-12115 published?
The CVE record for CVE-2026-12115 was published on June 17, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. 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-2026-12115 actively exploited?
CVE-2026-12115 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-12115?
CVE-2026-12115 has a CVSS base score of 6.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-12115?
No fix for CVE-2026-12115 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-12115 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-12115

Explore →

Is Your Infrastructure Affected by CVE-2026-12115?

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

Book a Demo →Browse All CVEs