CVE-2026-16573

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-05. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

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

The Bit Form WordPress plugin before 3.2.0 does not sanitize an uploaded signature image before storing it, allowing unauthenticated attackers to upload a crafted SVG file containing JavaScript that executes when the file is viewed, leading to Stored Cross-Site Scripting.

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

Published

August 5, 2026

Last Modified

August 5, 2026

Advisory Details (1)

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

Bit Form < 3.2.0 – Unauthenticated Stored XSS via SVG Signature Upload | CVE 2026-16573 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/a102e6ba-02f3-46cf-b496-f129ea3d9c8f/

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

Frequently asked(5)

What is CVE-2026-16573?
CVE-2026-16573 is a high vulnerability published on August 5, 2026. The Bit Form WordPress plugin before 3.2.0 does not sanitize an uploaded signature image before storing it, allowing unauthenticated attackers to upload a crafted SVG file containing JavaScript that executes when the file is viewed, leading to Stored Cross-Site Scripting.
When was CVE-2026-16573 disclosed?
CVE-2026-16573 was first published in the National Vulnerability Database on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16573 actively exploited?
CVE-2026-16573 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 81.1% of all scored CVEs.
What is the CVSS score of CVE-2026-16573?
CVE-2026-16573 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-16573?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16573, 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-16573

Explore →

Is Your Infrastructure Affected by CVE-2026-16573?

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