CVE-2026-81423

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-09-05. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 4.3; sources differ by 0.0.

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

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

The Accept Stripe Payments WordPress plugin before 2.1.4 does not validate a user-supplied URL before using it in a redirect, allowing unauthenticated attackers to redirect visitors to an arbitrary external website, which can be leveraged for phishing.

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

Published

September 5, 2026

Last Modified

September 8, 2026

Advisory Details (1)

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

Accept Stripe Payments < 2.1.4 – Open Redirect via IPN Handler | CVE 2026-81423 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/0e4bbbde-b93e-4b58-8baf-301073e9a0c5/

Vendor Advisories for CVE-2026-81423(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 / 44× 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-09-20 20:16 UTCEPSS rescore
  2. 2026-09-20 02:07 UTCEG score recompute
  3. 2026-09-20 02:07 UTCGHSA enrichment
  4. 2026-09-19 01:51 UTCEG score recompute
  5. 2026-09-19 01:51 UTCGHSA enrichment
  6. 2026-09-18 19:28 UTCEPSS rescore
  7. 2026-09-18 01:36 UTCEG score recompute
  8. 2026-09-18 01:36 UTCGHSA enrichment
  9. 2026-09-17 01:21 UTCEG score recompute
  10. 2026-09-17 01:21 UTCGHSA enrichment
  11. 2026-09-16 14:08 UTCEPSS rescore
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-16 01:06 UTCEG score recompute
  14. 2026-09-16 01:06 UTCGHSA enrichment
  15. 2026-09-15 03:12 UTCEPSS rescore
  16. 2026-09-15 03:12 UTCEPSS rescore
  17. 2026-09-15 00:51 UTCGHSA enrichment
  18. 2026-09-14 00:36 UTCEG score recompute
  19. 2026-09-14 00:36 UTCGHSA enrichment
  20. 2026-09-13 00:21 UTCEG score recompute
  21. 2026-09-13 00:21 UTCGHSA enrichment
  22. 2026-09-12 00:06 UTCEG score recompute
  23. 2026-09-12 00:06 UTCGHSA enrichment
  24. 2026-09-11 14:53 UTCEPSS rescore
  25. 2026-09-11 14:53 UTCEPSS rescore
Show 19 more
  1. 2026-09-10 23:50 UTCEG score recompute
  2. 2026-09-10 23:50 UTCGHSA enrichment
  3. 2026-09-09 23:21 UTCEG score recompute
  4. 2026-09-09 23:21 UTCGHSA enrichment
  5. 2026-09-08 22:01 UTCEPSS rescore
  6. 2026-09-08 19:55 UTCGHSA enrichment
  7. 2026-09-08 11:58 UTCEG score recompute
  8. 2026-09-08 11:57 UTCGHSA enrichment
  9. 2026-09-07 11:41 UTCEG score recompute
  10. 2026-09-07 11:41 UTCGHSA enrichment
  11. 2026-09-06 13:48 UTCEPSS rescore
  12. 2026-09-06 11:23 UTCGHSA enrichment
  13. 2026-09-06 10:46 UTCEG score recompute▲ 4.30
  14. 2026-09-06 10:45 UTCGHSA enrichment
  15. 2026-09-06 10:44 UTCMITRE cvelistV5CVSS v3 → 4.3 · severity → MEDIUM
  16. 2026-09-05 15:31 UTCEPSS rescore
  17. 2026-09-05 07:23 UTCNVD update
  18. 2026-09-05 06:36 UTCEG score recompute
  19. 2026-09-05 06:33 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81423?
CVE-2026-81423 is a medium vulnerability published on September 5, 2026. The Accept Stripe Payments WordPress plugin before 2.1.4 does not validate a user-supplied URL before using it in a redirect, allowing unauthenticated attackers to redirect visitors to an arbitrary external website, which can be leveraged for phishing.
When was CVE-2026-81423 disclosed?
CVE-2026-81423 was first published in the National Vulnerability Database on September 5, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81423 actively exploited?
CVE-2026-81423 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 88.1% of all scored CVEs.
What is the CVSS score of CVE-2026-81423?
CVE-2026-81423 has a CVSS v3.1 base score of 4.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-81423?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81423, 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-81423

Explore →

Is Your Infrastructure Affected by CVE-2026-81423?

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

Start Free Scan →Browse All CVEs