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

CVE-2025-60169

HIGH · 7.1 CVSS v3.1 Published 2025-09-26
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 W3S Cloud Technology W3SCloud Contact Form 7 to Zoho CRM w3s-cf7-zoho allows Stored XSS.This issue affects W3SCloud Contact Form 7 to Zoho CRM: from n/a through <= 3.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 W3SCloud Contact Form 7 to Zoho CRM WordPress plugin allows authenticated attackers to inject malicious JavaScript through Stored XSS. The lack of proper CSRF protection enables attackers to craft requests that, when triggered by an administrator session, cause persistent malicious scripts to be stored in the CRM integration settings or form submissions.

MitigationImplement anti-CSRF tokens (nonces) on all form submissions and administrative actions within the plugin. Additionally, apply proper input validation and output escaping on all user-supplied data before storing to Zoho CRM to prevent XSS. Update to the latest patched version when available.

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. Verify W3SCloud Contact Form 7 to Zoho CRM plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'W3SCloud Contact Form 7 to Zoho CRM' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder containing 'w3scloud' or 'cf7-to-zoho' in the name.
    Affected if The plugin is not installed on the WordPress site.
  2. Check the installed plugin version
    In WordPress admin_plugins list, click on the plugin to view its details and note the version number displayed. Compare this version to the affected version range provided in CVE-2025-60169.
    Affected if The installed version falls within the affected version range and has not been patched.
  3. Inspect Zoho CRM integration settings for stored scripts
    Navigate to the plugin settings page in WordPress admin (usually under Contact > CF7 to Zoho or a dedicated W3SCloud settings menu). Examine all text fields in the CRM integration configuration (API credentials, field mappings, custom headers) for unexpected script tags, iframe elements, or encoded characters that may indicate malicious JavaScript injection.
    Affected if Any CRM integration setting fields contain <script>, <img onerror>, <svg onload>, or other JavaScript event handlers that were not intentionally added by an administrator.
  4. Review recent form submissions for XSS payloads
    Access the plugin's form submission logs or the WordPress database (wp_posts table for entries created by the plugin) to inspect recent CRM sync records. Look for form data containing HTML tags, JavaScript event handlers, or encoded payloads that could represent attempted XSS injection.
    Affected if Form submission data sent to Zoho CRM contains unexpected HTML markup or JavaScript code.
  5. Verify CSRF nonce protection on plugin admin actions
    Access the plugin PHP files in /wp-content/plugins/ and search for 'wp_nonce_field', 'check_admin_referer', 'check_ajax_referer', or 'nonce' across all PHP files. Note whether these security tokens are present on forms that update CRM settings.
    Affected if The plugin lacks CSRF validation (nonces) on forms that modify CRM integration settings or where the nonce verification can be bypassed.

If the W3SCloud Contact Form 7 to Zoho CRM plugin is installed, the version is within the affected range, and the CRM integration settings or form submissions contain unexpected scripts, the environment is affected by CVE-2025-60169.

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

Implement anti-CSRF tokens (nonces) on all form submissions and administrative actions within the plugin. Additionally, apply proper input validation and output escaping on all user-supplied data before storing to Zoho CRM to prevent XSS. Update to the latest patched version when available.

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-60169 — 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-60169 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