The Formidable Forms WordPress plugin before 6.35 does not restrict who can set the identifier recording which user last edited a form entry, and relies on that identifier when deciding whether to strip HTML from stored entry values, allowing unauthenticated visitors to have markup rendered in the admin entry view that would otherwise be removed, and to attribute their submission to an administrator who never made it.
CVE-2026-85641
Score 4.3 from GitHub Security Advisory published 2026-09-16. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 4.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- 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 computedSeverity43% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 3%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 17, 2026
Advisory Details (1)
Auto-updated Sep 17, 2026Formidable Forms 6.34 – Unauthenticated Stored Content Injection via 'updated_by' Parameter | CVE 2026-85641 | Plugin Vulnerabilities
https://wpscan.com/vulnerability/99933e4e-e371-4ba4-ad41-6849fcc6a5eb/Vendor Advisories for CVE-2026-85641(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 16× in last 7d / 16× 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.
- 2026-09-19 13:13 UTCEG score recompute
- 2026-09-19 13:13 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 13:18 UTCEG score recompute
- 2026-09-18 13:18 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 13:23 UTCGHSA enrichment
- 2026-09-17 12:56 UTCEG score recompute▲ 4.30
- 2026-09-17 12:56 UTCGHSA enrichment
- 2026-09-17 12:54 UTCMITRE cvelistV5CVSS v3 → 4.3 · severity → MEDIUM
- 2026-09-16 21:01 UTCEG score recompute
- 2026-09-16 21:01 UTCGHSA enrichment
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 06:21 UTCNVD update
- 2026-09-16 06:03 UTCEG score recompute
- 2026-09-16 06:02 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-85641?
When was CVE-2026-85641 disclosed?
Is CVE-2026-85641 actively exploited?
What is the CVSS score of CVE-2026-85641?
How do I remediate CVE-2026-85641?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-85641
Is Your Infrastructure Affected by CVE-2026-85641?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.