CVE-2021-24444 json
TaxoPress < 3.0.7.2 - Authenticated Stored Cross-Site Scripting (XSS)
published 5y ago modified 4mo ago also EUVD-2021-11356
- cvss
- 4.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 1
- Exploit-DB
Summary
The TaxoPress – Create and Manage Taxonomies, Tags, Categories WordPress plugin before 3.0.7.2 does not sanitise its Taxonomy description field, allowing high privilege users to set JavaScript payload in them even when the unfiltered_html capability is disallowed, leading to an authenticated Stored Cross-Site Scripting issue.
Patch / fix
- taxopress taxopress 3.0.7.2
Is CVE-2021-24444 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-50442)
Exploit prediction
2.32% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-50442 WordPress Plugin TaxoPress 3.0.7.1 - Stored Cross-Site Scripting (XSS) (Authenticated) webapps, 2021-10-25
- wpscan.com https://wpscan.com/vulnerability/a31321fe-adc6-4480-a220-35aedca52b8b referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:P/A:N |
Affected products
- Unknown TaxoPress – Create and Manage Taxonomies, Tags, Categories
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
-
wpscan.com
/vulnerability/a31321fe-adc6-4480-a220-35aedca52b8b
exploit, third-party-advisory
-
packetstormsecurity.com
/files/164604/WordPress-TaxoPress-3.0.7.1-Cross-Site-Scripting.html
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2021-24444
- NVD CVE-2021-24444
Fencer Intel 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.