CVE-2021-24234 json
Ivory Search < 4.6.1 - Reflected Cross Site Scripting (XSS)
published 5y ago modified 4mo ago also EUVD-2021-11148
- cvss
- 6.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 67%
- public exploits
- 0
- none known
Summary
The Search Forms page of the Ivory Search WordPress lugin before 4.6.1 did not properly sanitise the tab parameter before output it in the page, leading to a reflected Cross-Site Scripting issue when opening a malicious crafted link as a high privilege user. Knowledge of a form id is required to conduct the attack.
Patch / fix
- ivorysearch ivory_search 4.6.1
Is CVE-2021-24234 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 FencerExploit prediction
1.17% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/ecc620be-8e29-4860-9d32-86b5814a3835 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
- Unknown Ivory Search – WordPress Search Plugin
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
-
wpscan.com
/vulnerability/ecc620be-8e29-4860-9d32-86b5814a3835
exploit, third-party-advisory
-
getastra.com
/blog/911/plugin-exploit/reflected-xss-vulnerability-in-ivory-search-wp-plugin/
third-party-advisory
-
jinsonvarghese.com
/reflected-xss-vulnerability-found-in-ivory-search-plugin/
third-party-advisory
Sources
- CVE List CVE-2021-24234
- NVD CVE-2021-24234
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.