CVE-2026-12901

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreHIGH confidence

Score 5.9 from GitHub Security Advisory published 2026-08-07. a secondary CVSS source baseline 5.9; sources differ by 0.0.

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

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

The GetPaid WordPress plugin before 2.8.55 does not verify the authenticity of incoming Worldpay payment notifications, allowing unauthenticated attackers to forge a notification that marks a pending invoice as paid without any payment being made.

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

Published

August 6, 2026

Last Modified

August 7, 2026

Advisory Details (1)

Auto-updated Aug 6, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

GetPaid < 2.8.55 – Unauthenticated Worldpay Payment Bypass via Insufficient IPN Verification | CVE 2026-12901 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/5eb54542-4119-4d4c-8e93-e0b23cb28ae5/

Vendor Advisories for CVE-2026-12901(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 20× in last 7d / 42× 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-21 06:37 UTCEG score recompute
  2. 2026-08-21 06:37 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 05:23 UTCEG score recompute
  5. 2026-08-20 05:23 UTCGHSA enrichment
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-19 04:09 UTCEG score recompute
  8. 2026-08-19 04:09 UTCGHSA enrichment
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-18 02:48 UTCEG score recompute
  11. 2026-08-18 02:48 UTCGHSA enrichment
  12. 2026-08-17 01:34 UTCEG score recompute
  13. 2026-08-17 01:34 UTCGHSA enrichment
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-16 00:20 UTCEG score recompute
  17. 2026-08-16 00:20 UTCGHSA enrichment
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 23:05 UTCEG score recompute
  20. 2026-08-14 23:05 UTCGHSA enrichment
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-13 21:51 UTCGHSA enrichment
  23. 2026-08-12 20:37 UTCEG score recompute
  24. 2026-08-12 20:37 UTCGHSA enrichment
  25. 2026-08-12 13:50 UTCEPSS rescore
Show 17 more
  1. 2026-08-11 19:23 UTCEG score recompute
  2. 2026-08-11 19:23 UTCGHSA enrichment
  3. 2026-08-11 13:42 UTCEPSS rescore
  4. 2026-08-10 23:59 UTCEPSS rescore
  5. 2026-08-10 18:09 UTCGHSA enrichment
  6. 2026-08-09 16:55 UTCEG score recompute
  7. 2026-08-09 16:55 UTCGHSA enrichment
  8. 2026-08-09 13:46 UTCEPSS rescore
  9. 2026-08-08 16:37 UTCEPSS rescore
  10. 2026-08-08 15:41 UTCEG score recompute
  11. 2026-08-08 15:41 UTCGHSA enrichment
  12. 2026-08-07 14:26 UTCEG score recompute
  13. 2026-08-07 14:26 UTCGHSA enrichment
  14. 2026-08-07 14:13 UTCEG score recompute
  15. 2026-08-07 14:13 UTCGHSA enrichment
  16. 2026-08-06 22:17 UTCEG score recompute
  17. 2026-08-06 22:15 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-12901?
CVE-2026-12901 is a medium vulnerability published on August 6, 2026. The GetPaid WordPress plugin before 2.8.55 does not verify the authenticity of incoming Worldpay payment notifications, allowing unauthenticated attackers to forge a notification that marks a pending invoice as paid without any payment being made.
When was CVE-2026-12901 disclosed?
CVE-2026-12901 was first published in the National Vulnerability Database on August 6, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12901 actively exploited?
CVE-2026-12901 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 97.4% of all scored CVEs.
What is the CVSS score of CVE-2026-12901?
CVE-2026-12901 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-12901?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12901, 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-12901

Explore →

Is Your Infrastructure Affected by CVE-2026-12901?

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

Start Free Scan →Browse All CVEs