CVE-2026-92098: webheadllc Webheadcoder advisory

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.

What it is

The Webheadcoder Multi-Step Forms for Contact Form 7 plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘l10n_print_after’ parameter in all versions up to, and including, 4.7 due to insufficient input sanitization and output escaping. 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 link. Successful exploitation requires that the targeted site has at least one Contact Form 7 form configured with a [multistep] form-tag, as the canonicalization introduced in version 4.7 blocks the attack path on non-multistep forms.

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

Weakness: CWE-79 Improper Neutralization of Input During Web Page Generation (‘Cross-site Scripting’)

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and a user must take an action. Impact: confidentiality low, integrity low, availability none. CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.985
strong exploit evidence
On CISA KEV: Not listed
Detection rule: Suricata

Who is affected

Product	Affected	Not affected
webheadllc Webheadcoder Multi-Step Forms for Contact Form 7	up to and including 4.7	Not 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-92098 WordPress CF7 Multi-Step Forms - l10n_print_after Reflected XSS. Add them to your Suricata rule set and reload.

Show the rules

suricata

# CVE-2026-92098 - Multi-Step Forms for Contact Form 7 (WordPress) <= 4.7 reflected XSS:
# the 'l10n_print_after' parameter is insufficiently sanitized and reflected (via the
# wp_localize_script inline-script sink) on sites with a [multistep] form, letting an
# unauthenticated attacker inject script. This matches a submission carrying an
# l10n_print_after parameter whose value contains a script/event-handler payload.
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-92098 WordPress CF7 Multi-Step Forms - l10n_print_after Reflected XSS"; flow:established,to_server; content:"l10n_print_after"; nocase; fast_pattern; pcre:"/l10n_print_after[^&]*(?:%3c|<)\s*(?:svg|script|img|iframe|on\w+\s*(?:%3d|=))|l10n_print_after[^&]*on(?:error|load|mouseover)\s*(?:%3d|=)/i"; classtype:web-application-attack; reference:cve,CVE-2026-92098; reference:url,https://www.exploit.observer/?keyword=CVE-2026-92098&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=wordpress&match=exact; sid:1098603; rev:1;)

CVE-2026-92098.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.