CVE-2024-6835 json
Ivory Search – WordPress Search Plugin <= 5.5.6 - Information Exposure via AJAX Search Form
published 2y ago modified 4mo ago also EUVD-2024-47845
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 44%
- public exploits
- 0
- none known
Summary
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. This makes it possible for unauthenticated attackers to extract text data from password-protected posts using the boolean-based attack on the AJAX search form
Patch / fix
Is CVE-2024-6835 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected products
- vinod-dalvi Ivory Search – WordPress Search Plugin
- ivorysearch ivory_search
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Technology feeds
References
-
plugins.trac.wordpress.org
/changeset/3145289/
patch
-
wordfence.com
/threat-intel/vulnerabilities/id/013f7c26-8348-4c54-af61-473a720a5095?source=cve
third-party-advisory
-
plugins.trac.wordpress.org
/browser/add-search-to-menu/tags/5.5.6/public/class-is-ajax.php#L45
product
-
plugins.trac.wordpress.org
/browser/add-search-to-menu/tags/5.5.6/public/partials/is-ajax-results.php#L57
product
Sources
- CVE List CVE-2024-6835
- NVD CVE-2024-6835
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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.