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

CVE-2025-32616

HIGH · 7.1 CVSS v3.1 Published 2025-04-09
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 nimbata Nimbata Call Tracking nimbata-call-tracking allows Stored XSS.This issue affects Nimbata Call Tracking: from n/a through <= 1.7.4.

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 Nimbata Call Tracking WordPress plugin (versions <= 1.7.4) allows attackers to inject malicious scripts via Stored XSS. An authenticated admin could be tricked into executing unintended actions through a crafted request, leading to persistent script injection.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing forms and AJAX endpoints, validate Origin/Referer headers, and apply proper output escaping/sanitization for stored data to prevent XSS.

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 Nimbata Call Tracking plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and search for 'Nimbata Call Tracking' or check the file system at /wp-content/plugins/ for a directory containing 'nimbata'
    Affected if The plugin directory exists in the WordPress installation
  2. Check installed plugin version
    In WordPress admin_plugins list, find the Nimbata Call Tracking entry and note the version number displayed, or read the 'Version' field from the plugin's main PHP file header
    Affected if Version number is 1.7.4 or lower
  3. Inspect plugin settings for suspicious scripts
    Navigate to the plugin settings page (usually under Settings or a dedicated Nimbata menu item) and examine all input fields for any unexpected script tags, iframe elements, or encoded JavaScript
    Affected if Any stored XSS payloads are present in plugin configuration fields
  4. Review plugin admin forms for nonce protection
    Examine the plugin's PHP source code in the admin directory, looking for wp_nonce_field or wp_nonce verification on state-changing forms and AJAX handlers
    Affected if State-changing forms lack nonce verification (wp_nonce_field is missing)
  5. Check WordPress activity logs for admin action anomalies
    If activity logging plugins are installed, review logs for unexpected settings changes or posts created around the time of potential social engineering attacks
    Affected if Unusual admin actions were performed that modified plugin settings

You are affected if the Nimbata Call Tracking plugin is installed and the version is 1.7.4 or lower, especially if admin forms lack CSRF token protection or unexpected scripts are already stored in plugin settings.

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 state-changing forms and AJAX endpoints, validate Origin/Referer headers, and apply proper output escaping/sanitization for stored data to prevent XSS.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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