CVE-2026-95817

HIGHPre-NVD 7.27.2—
EchelonGraph scoreHIGH confidence

Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-10-02. A secondary CVSS source baseline 7.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.2EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.2Exploit: 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 DoFollow Case by Case plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content in all versions up to, and including, 3.6.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Comment moderation delays but does not prevent exploitation — once an administrator approves the visually innocuous comment, the stored payload executes in the browser of every subsequent visitor to the affected post.

CVSS v3
7.2
EG Score
7.2HIGHhigh confidence
EG Risk
32
EG Risk 32/100CISA SSVC

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%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
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.2%
EPSS %ILE
13th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

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 (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 2, 2026

Last Modified

October 2, 2026

References (5)

Vendor Advisories for CVE-2026-95817(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 19× in last 7d / 19× 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-10-04 14:09 UTCGHSA enrichment
  2. 2026-10-04 03:09 UTCGHSA enrichment
  3. 2026-10-03 16:13 UTCEG score recompute
  4. 2026-10-03 16:13 UTCGHSA enrichment
  5. 2026-10-03 14:26 UTCEPSS rescore
  6. 2026-10-03 05:17 UTCGHSA enrichment
  7. 2026-10-02 18:20 UTCEG score recompute
  8. 2026-10-02 18:20 UTCGHSA enrichment
  9. 2026-10-02 18:20 UTCGHSA enrichment
  10. 2026-10-02 18:15 UTCGHSA enrichment
  11. 2026-10-02 18:15 UTCGHSA enrichment
  12. 2026-10-02 18:15 UTCEG score recompute
  13. 2026-10-02 18:15 UTCGHSA enrichment
  14. 2026-10-02 17:57 UTCEPSS rescore
  15. 2026-10-02 13:23 UTCEG score recompute
  16. 2026-10-02 13:23 UTCGHSA enrichment
  17. 2026-10-02 08:27 UTCEG score recompute
  18. 2026-10-02 07:47 UTCEG score recompute
  19. 2026-10-02 07:45 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-95817?
CVE-2026-95817 is a high vulnerability published on October 2, 2026. The DoFollow Case by Case plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content in all versions up to, and including, 3.6.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web…
When was CVE-2026-95817 disclosed?
CVE-2026-95817 was first published on October 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-95817 actively exploited?
CVE-2026-95817 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-95817?
CVE-2026-95817 has a CVSS base score of 7.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-95817?
No fix for CVE-2026-95817 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-95817 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-95817?

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

Book a Demo →Browse All CVEs