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

CVE-2025-58809

HIGH · 7.1 CVSS v3.1 Published 2025-09-05
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 Nick Ciske To Lead For Salesforce salesforce-wordpress-to-lead allows Reflected XSS.This issue affects To Lead For Salesforce: from n/a through <= 2.7.3.9.

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

CSRF vulnerability in the To Lead For Salesforce WordPress plugin allows attackers to inject malicious scripts via reflected XSS. The flaw exists in versions up to 2.7.3.9, where proper token validation is missing, enabling crafted requests to execute arbitrary JavaScript in victim browsers.

MitigationUpdate to the latest version of the plugin; until then, implement anti-CSRF tokens in forms and ensure all user-supplied data is properly sanitized before output.

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. Confirm plugin is installed
    Check for the 'to-lead-for-salesforce' directory in wp-content/plugins/ on the WordPress server, or list installed plugins via WP-CLI: wp plugin list --name='to-lead-for-salesforce'
    Affected if The plugin directory or listing is found on the server
  2. Determine installed version
    Read the plugin header from wp-content/plugins/to-lead-for-salesforce/to-lead-for-salesforce.php to extract the 'Version:' field, or run: wp plugin get to-lead-for-salesforce --field=version
    Affected if The version returned is 2.7.3.9 or any earlier version up to and including the first version of this plugin
  3. Identify exposed web forms
    Search the site for any HTML forms that post to endpoints containing 'to-lead', 'salesforce', or 'tlead' in the action attribute, or check WP admin under the plugin settings for active form configurations
    Affected if Any public-facing forms powered by this plugin are found and accessible to unauthenticated users
  4. Verify CSRF token presence in form handling
    Inspect the plugin source code in to-lead-for-salesforce.php and related files for nonce verification calls (wp_verify_nonce, check_admin_referer, or similar) when form submissions are processed
    Affected if No nonce verification or CSRF token validation is found in the form processing logic, or the validation can be bypassed

A user is affected if the To Lead For Salesforce plugin version is 2.7.3.9 or earlier and the plugin provides publicly accessible forms without CSRF token protection.

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 to the latest version of the plugin; until then, implement anti-CSRF tokens in forms and ensure all user-supplied data is properly sanitized before output.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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