CVE-2026-15939

LOWPre-NVD 2.72.7—
EchelonGraph scoreHIGH confidence

Score 2.7 from GitHub Security Advisory (severity: LOW) published 2026-08-02. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 2.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this weekElevated
2.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.7Exploit: Elevated riskExposed: 0

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

The Simple Restrict WordPress plugin before 1.2.9 does not enforce its content-restriction permission check on the REST API the way it does on the front end, relying there on a generic capability check instead of the Simple Restrict WordPress plugin before 1.2.9's own permission system, allowing users with contributor-level access or above to read the content of restricted posts and pages they were never granted access to.

CVSS v3
2.7
EG Score
2.7(high)
EG Risk
28(Track)
EG Risk 28/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
Severity27% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

August 2, 2026

Last Modified

August 5, 2026

References (1)

Vendor Advisories for CVE-2026-15939(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 11× in last 7d / 38× 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-08-20 22:55 UTCEPSS rescore
  2. 2026-08-19 19:41 UTCEG score recompute
  3. 2026-08-19 19:41 UTCGHSA enrichment
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-17 00:03 UTCEG score recompute
  8. 2026-08-17 00:03 UTCGHSA enrichment
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-16 02:14 UTCEPSS rescore
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-14 04:25 UTCEG score recompute
  13. 2026-08-14 04:25 UTCGHSA enrichment
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-12 13:50 UTCEPSS rescore
  16. 2026-08-11 13:42 UTCEPSS rescore
  17. 2026-08-11 08:47 UTCEG score recompute
  18. 2026-08-11 08:47 UTCGHSA enrichment
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-08 13:09 UTCEG score recompute
  22. 2026-08-08 13:09 UTCGHSA enrichment
  23. 2026-08-06 13:46 UTCEPSS rescore
  24. 2026-08-05 19:17 UTCEPSS rescore
  25. 2026-08-05 17:30 UTCEG score recompute
Show 13 more
  1. 2026-08-05 17:30 UTCGHSA enrichment
  2. 2026-08-05 16:52 UTCEG score recompute▲ 2.70
  3. 2026-08-05 16:52 UTCGHSA enrichment
  4. 2026-08-05 16:50 UTCMITRE cvelistV5CVSS v3 → 2.7 · severity → LOW
  5. 2026-08-05 02:17 UTCEG score recompute
  6. 2026-08-05 02:17 UTCGHSA enrichment
  7. 2026-08-04 15:10 UTCEPSS rescore
  8. 2026-08-04 10:38 UTCEPSS rescore
  9. 2026-08-03 10:35 UTCEPSS rescore
  10. 2026-08-02 06:36 UTCGHSA enrichment
  11. 2026-08-02 06:35 UTCNVD update
  12. 2026-08-02 06:07 UTCEG score recompute
  13. 2026-08-02 06:04 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-15939?
CVE-2026-15939 is a low vulnerability published on August 2, 2026. The Simple Restrict WordPress plugin before 1.2.9 does not enforce its content-restriction permission check on the REST API the way it does on the front end, relying there on a generic capability check instead of the Simple Restrict WordPress plugin before 1.2.9's own permission system, allowing…
When was CVE-2026-15939 disclosed?
CVE-2026-15939 was first published in the National Vulnerability Database on August 2, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15939 actively exploited?
CVE-2026-15939 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.3% of all scored CVEs.
What is the CVSS score of CVE-2026-15939?
CVE-2026-15939 has a CVSS v3.1 base score of 2.7 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-15939?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15939, 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-2026-15939

Explore →

Is Your Infrastructure Affected by CVE-2026-15939?

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

Start Free Scan →Browse All CVEs