Unauthenticated Broken Access Control in Simple Payment <= 2.5.2 versions.
CVE-2026-81767
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 38(Track)EG Risk 38/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 computedSeverity75% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 10%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
August 28, 2026
Advisory Details (1)
Auto-updated Aug 28, 2026Broken Access Control in WordPress Simple Payment Plugin - Patchstack
https://patchstack.com/database/wordpress/plugin/simple-payment/vulnerability/wordpress-simple-payment-plugin-2-5-2-broken-access-control-vulnerability?_s_id=cveVendor Advisories for CVE-2026-81767(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 / 11× 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.
- 2026-08-30 05:00 UTCEG score recompute
- 2026-08-30 05:00 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 18:10 UTCGHSA enrichment
- 2026-08-29 07:19 UTCGHSA enrichment
- 2026-08-28 20:27 UTCGHSA enrichment
- 2026-08-28 18:42 UTCEG score recompute
- 2026-08-28 18:42 UTCGHSA enrichment
- 2026-08-28 16:32 UTCEG score recompute
- 2026-08-28 15:28 UTCEG score recompute
- 2026-08-28 15:25 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p90CRITICAL
- CVE-2018-1217EG 9.8EPSS p97CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-81767?
When was CVE-2026-81767 disclosed?
Is CVE-2026-81767 actively exploited?
What is the CVSS score of CVE-2026-81767?
How do I remediate CVE-2026-81767?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-81767
Is Your Infrastructure Affected by CVE-2026-81767?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.