CVE-2021-24276 json
Contact Form by Supsystic < 1.7.15 - Reflected Cross-Site scripting (XSS)
published 2021-05-05 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-11190
- cvss
- 6.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 16.0%
- EPSS 16.0% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
The Contact Form by Supsystic WordPress plugin before 1.7.15 did not sanitise the tab parameter of its options page before outputting it in an attribute, leading to a reflected Cross-Site Scripting issue
Patch / fix
- supsystic contact_form 1.7.15
Timeline
- Published
- First public exploit (EDB-50344)
Exploit prediction
16.04% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-50344 WordPress Plugin Contact Form 1.7.14 - Reflected Cross-Site Scripting (XSS) webapps, 2021-09-28
- Nuclei template WordPress Supsystic Contact Form <1.7.15 - Cross-Site Scripting nuclei detection template
- wpscan.com https://wpscan.com/vulnerability/1301123c-5e63-432a-ab90-3221ca532d9c referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/164308/WordPress-Contact-Form-1.7.14-Cross-Site-Scripting.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Affected products
- Supsystic Contact Form by Supsystic
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
-
wpscan.com
/vulnerability/1301123c-5e63-432a-ab90-3221ca532d9c
exploit, third-party-advisory
-
packetstormsecurity.com
/files/164308/WordPress-Contact-Form-1.7.14-Cross-Site-Scripting.html
exploit, third-party-advisory, vdb-entry
Sources
- CVE List CVE-2021-24276
- NVD CVE-2021-24276
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.