dbcve.org
Contact FormWordPress extension · Wpforms

CVE-2023-30500

MEDIUM · 6.1 CVSS v3.1 Published 2023-06-22
Fix available
A fix is available. Upgrade to after 1.8.1.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in WPForms WPForms Lite (wpforms-lite), WPForms WPForms Pro (wpforms) plugins <= 1.8.1.2 versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An unauthenticated reflected cross-site scripting (XSS) vulnerability exists in WPForms Lite and Pro plugins versions 1.8.1.2 and below. The vulnerability allows attackers to inject malicious JavaScript through unsanitized URL parameters that are reflected back in the application's response.

MitigationUpdate WPForms plugin to the latest version which contains proper input sanitization and output encoding for user-supplied parameters.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Contact FormWordPress extension
Affected:<= 1.8.1.2
WpformsWordPress extension
Affected:<= 1.8.1.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check WPForms plugin version in WordPress admin
    Navigate to WordPress Admin > Plugins > Installed Plugins. Locate WPForms Lite or WPForms (Pro) and view the version number displayed under the plugin name.
    Affected if The displayed version is 1.8.1.2 or lower
  2. Check WPForms version via plugin file
    Access the WordPress site via FTP or file manager. Navigate to /wp-content/plugins/wpforms/ and open the primary plugin file (wpforms.php or wpforms-lite.php). Locate the version header in the plugin file comments.
    Affected if The Version: field in the file header shows 1.8.1.2 or lower
  3. Verify WPForms plugin is active
    In WordPress Admin > Plugins > Installed Plugins, confirm that WPForms Lite or WPForms is currently activated.
    Affected if The plugin is active and the version is 1.8.1.2 or lower (the XSS only affects active installations)
  4. Confirm WordPress version is not mitigating the issue
    Check that WordPress core is not running a version that includes automatic XSS protection for plugins. This check is informational only as WordPress core does not provide plugin-level XSS protection.
    Affected if This is informational; the vulnerability exists in the plugin regardless of WordPress version

You are affected if WPForms Lite or Pro plugin is active and the installed version is 1.8.1.2 or lower.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.8.1.2
Interim mitigation

Update WPForms plugin to the latest version which contains proper input sanitization and output encoding for user-supplied parameters.

Recommended fix High confidence

WPForms version 1.8.2 or later (latest stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate WPForms (wpforms-lite for Lite version, or wpforms for Pro version)
  4. Click on 'Update now' if an update is available, or click 'Delete' and reinstall the latest version from the WordPress plugin repository
  5. After updating, verify the plugin version is greater than 1.8.1.2
  6. Test the contact forms on your site to ensure functionality remains intact
Caveat Minor: Review form functionality after upgrade as with any plugin update; no major breaking changes expected for this security patch

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Contact Form Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-30500 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-30500 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data