CVE-2026-16573: Bit Form (WordPress plugin) · Cross-Site Scripting (XSS)
Affects Bit Form (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 3.2.0 soon.
Data as of 3 Nov 2026, 22:58 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.2.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Upgrade Bit Form (WordPress plugin) to 3.2.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Bit Form | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, restrict or monitor uploads of SVG files and consider disabling signature image uploads if feasible. Implement additional input validation or sanitization on uploaded files as a temporary mitigation.
Description
Bit Form WordPress plugin versions before 3.2.0 contain a stored cross-site scripting (XSS) vulnerability. This occurs because the plugin does not sanitize uploaded signature images, allowing unauthenticated attackers to upload crafted SVG files with embedded JavaScript. When these SVG files are viewed, the malicious script executes, potentially compromising confidentiality, integrity, and availability.