WordPress Contact Form by WPForms plugin <= 2.0.3 - Cross Site Scripting (XSS) vulnerability
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.0.3.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. WordPress Contact Form by WPForms plugin version 2.0.3 or earlier (wpforms-lite)
- Exploitation0/40No signal
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
CVE-2026-54851 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects Contact Form by WPForms; fixed in 2.0.3.1.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.15% · 3rd percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 19/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 2.0.3.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The Contact Form by WPForms WordPress plugin has a reflected cross-site scripting flaw that lets an attacker run malicious scripts in a victim's browser. An attacker can reach it remotely without logging in, but a user must first interact with a crafted request or link.
Read the original description
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Awesomemotive Contact Form by WPForms wpforms-lite allows Reflected XSS.This issue affects Contact Form by WPForms: from n/a through 2.0.3.
What to do
Check whether your setup matches what the bug needs.
WordPress Contact Form by WPForms plugin version 2.0.3 or earlier (wpforms-lite)Upgrade to a fixed version: 2.0.3.1.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- wpforms-lite
through 2.0.3
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-54851
Is CVE-2026-54851 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The plugin fails to properly sanitize some input, which lets an attacker inject malicious scripts into pages of the site. Those scripts can run in visitors' browsers and steal visitor data or hijack their accounts.Source: patchstack.com, cve.org
Which versions are affected by CVE-2026-54851?
wpforms-lite: through 2.0.3.Source: cve.now feed data
Am I affected, and how do I check?
Versions of the WPForms Lite plugin (wpforms-lite, sold as Contact Form by WPForms) up to and including 2.0.3 are listed as vulnerable. To check, open the Plugins screen in WordPress admin and read the version shown next to Contact Form by WPForms.Source: patchstack.com, cve.org
How do I fix CVE-2026-54851?
Update the plugin to the latest available version, at least 2.0.3.1, as the vendor advises.Source: patchstack.com, cve.org