dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-40764

HIGH · 8.1 CVSS v3.1 Published 2026-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
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
Cross-Site Request Forgery (CSRF) vulnerability in Syed Balkhi Contact Form by WPForms wpforms-lite allows Cross Site Request Forgery.This issue affects Contact Form by WPForms: from n/a through <= 1.10.0.2.

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the WPForms Lite plugin versions up to 1.10.0.2 allows attackers to trick authenticated users into performing unintended actions by tricking their browsers into sending malicious requests. This occurs due to missing or insufficient anti-CSRF token validation on form submissions.

MitigationUpdate WPForms Lite plugin to the latest version beyond 1.10.0.2 which should contain the patch. If immediate update is not possible, implement additional CSRF protections such as anti-CSRF tokens on all form actions.

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

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
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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. Verify WPForms Lite plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for WPForms Lite in the list. Alternatively, check the /wp-content/plugins/wpforms-lite/ directory exists.
    Affected if WPForms Lite plugin is present in the WordPress installation
  2. Check installed WPForms Lite version
    In WordPress admin, go to Plugins > Installed Plugins > WPForms Lite and view the version number. Alternatively, check the version in the plugin header of wpforms-lite.php file in /wp-content/plugins/wpforms-lite/
    Affected if Installed version is 1.10.0.2 or any version prior to it (1.x.x series up to 1.10.0.2)
  3. Confirm form submissions are possible
    Verify that any forms have been created and are active on the site. In WPForms admin, check that forms exist under WPForms > All Forms and are published (status is not draft).
    Affected if At least one published form exists that accepts user submissions, making the CSRF vulnerability applicable to those form endpoints
  4. Inspect form action endpoints for CSRF protection
    Use browser developer tools or examine HTML source of a published WPForms form. Look for a hidden nonce field (typically named _wpnonce or similar) in the form HTML. Check if the form action submits to /wp-admin/admin-ajax.php or similar endpoints.
    Affected if Form HTML lacks a nonce token or anti-CSRF token field, indicating insufficient CSRF protection on form submissions

The site is affected if WPForms Lite version 1.10.0.2 or earlier is installed AND forms are published and accepting submissions without proper nonce validation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WPForms Lite plugin to the latest version beyond 1.10.0.2 which should contain the patch. If immediate update is not possible, implement additional CSRF protections such as anti-CSRF tokens on all form actions.

Recommended fix Moderate confidence

Latest version of WPForms Lite (Contact Form by WPForms) - version higher than 1.10.0.2

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'WPForms Lite' (Contact Form by WPForms)
  4. Check if an update is available. If so, update to the latest version
  5. Alternatively, you can update via WP-CLI: wp plugin update wpforms-lite
  6. After updating, verify the form functionality works correctly
Caveat Minor - review plugin changelog for any template or settings changes between your current version and the new version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40764 — 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-2026-40764 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