Ivorysearch is a search-related application with a narrow vulnerability footprint centered on its core product, where the disclosed issues cluster around web-application input handling and information exposure. The recurring weakness classes—cross-site scripting and sensitive information leakage—reflect common risks in web-facing applications. Current severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Ivorysearch over time
Signals from CVEs in this vendor scope (5 CVEs).
5 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2021-36869MEDIUM Reflected Cross-Site Scripting (XSS) vulnerability in WordPress Ivory Search plugin (versions <= 4.6.6). Vulnerable parameter: &post. | Oct 21, 2021 | 6.1 | 21 | NO | NO |
CVE-2021-24234MEDIUM 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 S | Apr 22, 2021 | 6.1 | 20 | NO | NO |
CVE-2021-25105MEDIUM The Ivory Search WordPress plugin before 5.4.1 does not escape some of the Form settings, which could allow high privilege users to perform Cross-Site Scripting attacks even when t | Feb 7, 2022 | 4.8 | 19 | NO | NO |
CVE-2024-6835MEDIUM The Ivory Search – WordPress Search Plugin plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 5.5.6 via the ajax_load_posts function. | Sep 5, 2024 | 5.3 | 17 | NO | NO |
CVE-2025-5209MEDIUM The Ivory Search WordPress plugin before 5.5.10 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Cross-Site Scrip | Jun 17, 2025 | 4.8 | 16 | NO | NO |
Signals from CVEs in this vendor scope (5 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Ivorysearch.
Media articles that mention a CVE ID that affects a product developed by Ivorysearch — matched by CVE ID, not by vendor name.