CVE-2026-14281

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-25. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.8Exploit: Elevated riskExposed services: Not assessed

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

The Automation Web Platform – Notifications and OTP for WooCommerce, Advanced Country Code plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 4.8.6. This is due to missing permission enforcement on the publicly accessible REST route POST /wp-json/wawp/v1/signup/ and the absence of a key allowlist in the finish_registration_logic function, which copies the attacker-controlled wawp_custom_fields parameter directly into update_user_meta() — allowing sensitive meta keys such as wp_capabilities and wp_user_level to be set by the caller. This makes it possible for unauthenticated attackers to register a new account with the administrator role and gain full administrative access to the site. When OTP verification is enabled at signup, the OTP session token (otp_transient) is returned in plaintext in the HTTP response body, and the handle_magic_link_request() handler marks that token as verified on any unauthenticated GET request containing it without ever checking the OTP code value — making the OTP step trivially bypassable with no inbox or SMS access required.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
75
EG Risk 75/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
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

September 25, 2026

Last Modified

September 25, 2026

References (14)

Vendor Advisories for CVE-2026-14281(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 55× in last 7d / 79× 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 12:46 UTCGHSA enrichment
  2. 2026-10-04 08:48 UTCGHSA enrichment
  3. 2026-10-04 04:48 UTCGHSA enrichment
  4. 2026-10-04 00:49 UTCGHSA enrichment
  5. 2026-10-03 20:50 UTCGHSA enrichment
  6. 2026-10-03 16:52 UTCEG score recompute
  7. 2026-10-03 16:51 UTCGHSA enrichment
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-03 12:53 UTCGHSA enrichment
  10. 2026-10-03 08:54 UTCGHSA enrichment
  11. 2026-10-03 04:55 UTCGHSA enrichment
  12. 2026-10-03 00:56 UTCGHSA enrichment
  13. 2026-10-02 20:58 UTCGHSA enrichment
  14. 2026-10-02 16:59 UTCEG score recompute
  15. 2026-10-02 16:59 UTCGHSA enrichment
  16. 2026-10-02 13:01 UTCGHSA enrichment
  17. 2026-10-02 09:02 UTCGHSA enrichment
  18. 2026-10-02 05:02 UTCGHSA enrichment
  19. 2026-10-02 01:03 UTCGHSA enrichment
  20. 2026-10-01 21:01 UTCEG score recompute
  21. 2026-10-01 21:01 UTCGHSA enrichment
  22. 2026-10-01 19:49 UTCEPSS rescore
  23. 2026-10-01 17:01 UTCGHSA enrichment
  24. 2026-10-01 12:32 UTCGHSA enrichment
  25. 2026-10-01 08:33 UTCGHSA enrichment
Show 54 more
  1. 2026-10-01 04:32 UTCGHSA enrichment
  2. 2026-10-01 00:34 UTCGHSA enrichment
  3. 2026-09-30 20:34 UTCGHSA enrichment
  4. 2026-09-30 16:36 UTCEG score recompute
  5. 2026-09-30 16:36 UTCGHSA enrichment
  6. 2026-09-30 15:02 UTCEPSS rescore
  7. 2026-09-30 11:47 UTCGHSA enrichment
  8. 2026-09-30 07:48 UTCGHSA enrichment
  9. 2026-09-30 03:49 UTCGHSA enrichment
  10. 2026-09-29 23:50 UTCGHSA enrichment
  11. 2026-09-29 17:06 UTCEG score recompute
  12. 2026-09-29 17:06 UTCGHSA enrichment
  13. 2026-09-29 15:20 UTCEPSS rescore
  14. 2026-09-29 13:07 UTCGHSA enrichment
  15. 2026-09-29 09:06 UTCGHSA enrichment
  16. 2026-09-29 05:03 UTCGHSA enrichment
  17. 2026-09-29 01:05 UTCEG score recompute
  18. 2026-09-29 01:04 UTCGHSA enrichment
  19. 2026-09-28 21:05 UTCGHSA enrichment
  20. 2026-09-28 17:06 UTCEG score recompute
  21. 2026-09-28 17:06 UTCGHSA enrichment
  22. 2026-09-28 13:51 UTCEPSS rescore
  23. 2026-09-28 13:08 UTCEG score recompute
  24. 2026-09-28 13:08 UTCGHSA enrichment
  25. 2026-09-28 09:09 UTCGHSA enrichment
  26. 2026-09-28 05:10 UTCGHSA enrichment
  27. 2026-09-28 01:12 UTCGHSA enrichment
  28. 2026-09-27 21:13 UTCGHSA enrichment
  29. 2026-09-27 17:14 UTCEG score recompute
  30. 2026-09-27 17:14 UTCGHSA enrichment
  31. 2026-09-27 13:47 UTCEPSS rescore
  32. 2026-09-27 13:15 UTCGHSA enrichment
  33. 2026-09-27 09:17 UTCGHSA enrichment
  34. 2026-09-27 05:18 UTCGHSA enrichment
  35. 2026-09-27 01:18 UTCGHSA enrichment
  36. 2026-09-26 21:19 UTCGHSA enrichment
  37. 2026-09-26 17:19 UTCEG score recompute
  38. 2026-09-26 17:19 UTCGHSA enrichment
  39. 2026-09-26 15:58 UTCEPSS rescore
  40. 2026-09-26 13:21 UTCGHSA enrichment
  41. 2026-09-26 09:19 UTCGHSA enrichment
  42. 2026-09-26 05:19 UTCGHSA enrichment
  43. 2026-09-26 01:18 UTCEG score recompute
  44. 2026-09-26 01:18 UTCGHSA enrichment
  45. 2026-09-25 21:19 UTCGHSA enrichment
  46. 2026-09-25 17:18 UTCGHSA enrichment
  47. 2026-09-25 13:19 UTCGHSA enrichment
  48. 2026-09-25 11:39 UTCEG score recompute
  49. 2026-09-25 11:39 UTCGHSA enrichment
  50. 2026-09-25 10:44 UTCEG score recompute
  51. 2026-09-25 10:44 UTCGHSA enrichment
  52. 2026-09-25 07:28 UTCEG score recompute
  53. 2026-09-25 07:02 UTCEG score recompute
  54. 2026-09-25 07:01 UTCMITRE cvelistV5first tracked

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCmurrez/CVE-2026-14281
    First seen Sep 25, 2026

    Unauthenticated privilege escalation in WordPress WAWP (Automation Web Platform) ≤ 4.8.6 via public REST signup and unsanitized wawp_custom_fields → admin. Python check/exploit PoC (PoCbit).

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-14281?
CVE-2026-14281 is a critical vulnerability published on September 25, 2026. The Automation Web Platform – Notifications and OTP for WooCommerce, Advanced Country Code plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 4.8.6. This is due to missing permission enforcement on the publicly accessible REST route POST…
When was CVE-2026-14281 disclosed?
CVE-2026-14281 was first published on September 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14281 actively exploited?
CVE-2026-14281 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-14281?
CVE-2026-14281 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-14281?
No fix for CVE-2026-14281 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-14281 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-14281?

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

Book a Demo →Browse All CVEs