CVE-2026-96574

MEDIUMPre-NVD 6.46.4
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.4 from GitHub Security Advisory published 2026-10-10. A secondary CVSS source baseline 6.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
6.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.4Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (Wordfence) lists wedevs User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission versions up to and including 4.3.12 as affected. No release containing a fix is confirmed on record.

The User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'wpuf_payment_method' parameter in all versions up to, and including, 4.3.12 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The bypass technique involves appending a valid gateway keyword such as 'bank' to the HTML payload, causing sanitize_text_field() to yield only the keyword for routing purposes while the full malicious raw value is stored and later rendered unescaped.

CVSS v3
6.4
EG Score
6.4MEDIUMhigh confidence
EG Risk
29
EG Risk 29/100

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 (value × EchelonGraph’s weight)
Severity64% × 45%
The EG Score, 6.4 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
11th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 10, 2026

Last Modified

October 13, 2026

References (7)

Vendor Advisories for CVE-2026-96574(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 / 19× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  2. 2026-10-13 13:52 UTCEG score recompute
  3. 2026-10-13 13:51 UTCGHSA enrichmentGHSA-49jc-5c97-fh4p · GitHub CVSS 6.4
  4. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  5. 2026-10-12 14:40 UTCEG score recompute
  6. 2026-10-11 19:11 UTCEG score recompute
  7. 2026-10-11 16:27 UTCEG score recompute
  8. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  9. 2026-10-11 13:39 UTCEG score recompute
  10. 2026-10-11 13:23 UTCEG score recompute
  11. 2026-10-11 13:23 UTCGHSA enrichmentGHSA-49jc-5c97-fh4p · GitHub CVSS 6.4
  12. 2026-10-11 12:47 UTCEG score recompute
  13. 2026-10-11 12:47 UTCGHSA enrichmentGHSA-49jc-5c97-fh4p · GitHub CVSS 6.4
  14. 2026-10-11 06:22 UTCEG score recompute
  15. 2026-10-11 06:22 UTCGHSA enrichmentGHSA-49jc-5c97-fh4p · GitHub CVSS 6.4
  16. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  17. 2026-10-10 07:23 UTCEG score recompute
  18. 2026-10-10 07:01 UTCEG score recomputeFirst assessed: 6.4 MEDIUM
  19. 2026-10-10 07:00 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-96574?
CVE-2026-96574 is a medium-severity vulnerability; its CVE record was published on October 10, 2026. The User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'wpufpaymentmethod' parameter in all versions up to, and including, 4.3.12 due to…
When was the CVE record for CVE-2026-96574 published?
The CVE record for CVE-2026-96574 was published on October 10, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 13, 2026; the record at its source may have been updated since.
Is CVE-2026-96574 actively exploited?
CVE-2026-96574 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-96574?
CVE-2026-96574 has a CVSS base score of 6.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-96574?
No fix for CVE-2026-96574 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 CVE record's CNA (Wordfence) lists wedevs User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission versions up to and including 4.3.12 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-96574 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-96574?

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

Book a Demo →Browse All CVEs