CVE-2026-116522: Relevanssi <= 4.28.5 - Unauthenticated Stored Cross-Site Scripting via Comment Content via Late Entity Decode

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-17 06:13 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

The Relevanssi, A Better Search plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘comment’ parameter in all versions up to, and including, 4.28.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the site to have both the comment indexing and comment highlighting options enabled, and the payload only fires when a visitor reaches a singular page via a Relevanssi search-result permalink carrying the highlight query parameter.

Description quoted from the CVE record (assigned by Wordfence, published 2026-10-31).

Weakness: CWE-79 Improper Neutralization of Input During Web Page Generation

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality low, integrity low, availability none. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Exploit Observer found 3 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 6 references on Exploit Observer

Live scores

EPSS
0.002
low predicted chance of attack
VEDAS
0.986
strong exploit evidence
On CISA KEV
Not listed
Detection rule
Suricata

Who is affected

ProductAffectedNot affected
Comesio Relevanssi, A Better Searchup to and including 4.28.5Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.

How to detect it

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-116522 Relevanssi - Stored XSS via Comment. Add them to your Suricata rule set and reload.

Show the rules
suricata
# CVE-2026-116522 - Relevanssi "A Better Search" WordPress plugin <= 4.28.5 stored XSS.
# An unauthenticated attacker submits a blog comment whose content carries HTML/JS; with
# comment indexing + highlighting enabled the payload is later reflected unescaped on a
# singular page reached via a Relevanssi search permalink. Storing is the standard WP
# comment POST, so this matches the unauthenticated comment-submission request shape.
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-116522 Relevanssi - Stored XSS via Comment"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/wp-comments-post.php"; nocase; fast_pattern; http.request_body; content:"comment"; nocase; pcre:"/(?:^|&)comment=[^&]*(?:(?:%3c|<)\s*(?:script|svg|img|iframe|details|body)|on(?:error|load|click|mouseover|focus|toggle)\s*(?:=|%3d))/i"; classtype:web-application-attack; reference:cve,CVE-2026-116522; reference:url,https://www.exploit.observer/?keyword=CVE-2026-116522&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=relevanssi&match=exact; sid:1104800; rev:1;)

CVE-2026-116522.rules on GitHub

References

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.

Supporting partners