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

CVE-2025-32922

HIGH · 7.1 CVSS v3.1 Published 2025-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/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 Saleswonder Team: Tobias WP2LEADS wp2leads allows Stored XSS.This issue affects WP2LEADS: from n/a through <= 3.5.0.

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

A Cross-Site Request Forgery (CSRF) vulnerability in the WP2LEADS WordPress plugin (version 3.5.0 and below) allows attackers to craft malicious requests that result in Stored XSS. This occurs because the plugin lacks proper CSRF protection, enabling attackers to inject persistent malicious scripts into the application that execute when other users view the affected content.

MitigationUpdate WP2LEADS to the latest patched version. Additionally, implement anti-CSRF tokens on all state-changing forms and actions within the plugin.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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. Locate WP2LEADS plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and search for 'WP2LEADS', or inspect the /wp-content/plugins/ directory for a folder named 'wp2leads' or similar
    Affected if WP2LEADS plugin is present in the WordPress installation
  2. Identify installed WP2LEADS version
    In WordPress admin Plugins page, find WP2LEADS and note the version number displayed below the plugin name, or read the 'Version:' field from the plugin's main PHP file header in /wp-content/plugins/wp2leads/
    Affected if The displayed version is 3.5.0 or any version lower than 3.5.0
  3. Confirm plugin is active
    In WordPress admin Plugins page, verify that WP2LEADS shows as 'Active' rather than 'Inactive' or 'Not installed'
    Affected if WP2LEADS is both installed and activated
  4. Identify state-changing forms
    Review the plugin's admin interface for any forms that modify data: settings pages, configuration forms, data submission forms, or any action that stores user input into the database
    Affected if The plugin has active forms or actions without visible anti-CSRF token implementation (tokens named 'nonce' or similar)

A WordPress site is affected if WP2LEADS plugin version 3.5.0 or lower is installed and active, exposing stored data to potential CSRF-to-Stored XSS attacks.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WP2LEADS to the latest patched version. Additionally, implement anti-CSRF tokens on all state-changing forms and actions within the plugin.

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-2025-32922 — 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-2025-32922 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