CVE-2026-19985 json
Relevanssi <= 4.28.1 - Reflected Cross-Site Scripting
published last mo. modified last mo. also EUVD-2026-75937
- cvss
- 6.1
- 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 40%
- public exploits
- 0
- none known
Summary
The Relevanssi – A Better Search plugin for WordPress is vulnerable to Reflected Cross-Site Scripting in versions up to, and including, 4.28.1 via the 's', 'post_types', and 'orderby' request parameters. This is due to insufficient input sanitization and output escaping in the relevanssi_debug_array() function in lib/debug.php, which dumps user-supplied query variables through print_r() inside a <pre> block without HTML escaping. The debug path is enabled by supplying the relevanssi_debug=on request parameter when the administrator has previously enabled the 'Debugging mode' setting; the gate itself is a configuration check with no capability, nonce, or logged-in check (the vendor explicitly suppresses nonce verification on that line). This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a specially crafted link.
Is CVE-2026-19985 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
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected products
- comesio Relevanssi – A Better Search
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/d07fe28c-f76e-42b2-b894-be316004235a?source=cve
- plugins.trac.wordpress.org /browser/relevanssi/tags/4.27.2/lib/search.php#L132
- plugins.trac.wordpress.org /browser/relevanssi/tags/4.27.2/lib/search.php#L143
- plugins.trac.wordpress.org /browser/relevanssi/tags/4.28.1/lib/debug.php#L68
- plugins.trac.wordpress.org /browser/relevanssi/tags/4.28.1/lib/search.php#L132
- plugins.trac.wordpress.org /browser/relevanssi/tags/4.28.1/lib/search.php#L143
- plugins.trac.wordpress.org /browser/relevanssi/tags/4.28.1/lib/debug.php#L27
- plugins.trac.wordpress.org /browser/relevanssi/tags/4.28.1/lib/search.php#L562
- plugins.trac.wordpress.org /browser/relevanssi/tags/4.27.2/lib/debug.php#L68
- plugins.trac.wordpress.org /browser/relevanssi/tags/4.27.2/lib/debug.php#L27
- plugins.trac.wordpress.org /browser/relevanssi/tags/4.27.2/lib/search.php#L562
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&new=3650355%40relevanssi%2Ftrunk&old=3529670%40relevanssi%2Ftrunk&s
Sources
- CVE List CVE-2026-19985
- NVD CVE-2026-19985
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.