CVE-2026-12501

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

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

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

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

The WP Travel Engine WordPress plugin before 6.8.2 does not verify that an incoming PayPal payment notification was sent to the site's configured merchant account, nor that the paid amount matches the order total, before marking a booking as paid, allowing unauthenticated attackers to mark bookings as fully paid using a token payment made to an attacker-controlled account.

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
55(Attend)
EG Risk 55/100SSVC: Attend

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
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
5%
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

WP Travel Engine < 6.8.2 – Unauthenticated Payment Bypass via Missing PayPal IPN Receiver and Amount Verification | CVE 2026-12501 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/3959ea5e-9670-4087-9506-44ba95c6a462/

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

Frequently asked(5)

What is CVE-2026-12501?
CVE-2026-12501 is a medium vulnerability published on August 6, 2026. The WP Travel Engine WordPress plugin before 6.8.2 does not verify that an incoming PayPal payment notification was sent to the site's configured merchant account, nor that the paid amount matches the order total, before marking a booking as paid, allowing unauthenticated attackers to mark bookings…
When was CVE-2026-12501 disclosed?
CVE-2026-12501 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-12501 actively exploited?
CVE-2026-12501 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 94.7% of all scored CVEs.
What is the CVSS score of CVE-2026-12501?
CVE-2026-12501 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-12501?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12501, 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-12501

Explore →

Is Your Infrastructure Affected by CVE-2026-12501?

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

Start Free Scan →Browse All CVEs