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

CVE-2025-23745

HIGH · 7.1 CVSS v3.1 Published 2025-01-16
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 Tussendoor B.V. Call me Now call-me-now allows Stored XSS.This issue affects Call me Now: from n/a through <= 1.0.5.

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

CSRF vulnerability in Tussendoor B.V. Call me Now plugin (versions up to 1.0.5) allows authenticated administrators to be tricked into submitting malicious requests that inject and store XSS payloads into the application, which then execute when other users view the compromised content.

MitigationUpdate to the latest patched version of the Call Me Now plugin. Additionally, implement anti-CSRF tokens for state-changing operations and ensure all user-supplied data is properly sanitized on input and encoded on 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. Verify Call me Now plugin is installed
    Access WordPress admin dashboard, navigate to Plugins section, or inspect the wp-content/plugins directory for the 'call-me-now' or 'tussendoor-call-me-now' folder
    Affected if The plugin folder exists in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Call me Now, and read the version number displayed; alternatively, open the main plugin PHP file and look for the 'Version' header in the plugin comment block
    Affected if The version number is 1.0.5 or lower (any version 'up to 1.0.5' is affected)
  3. Inspect plugin settings for stored XSS payloads
    Navigate to the Call me Now plugin settings page in the WordPress admin panel; examine all input fields (such as call button text, messages, or configuration options) for suspicious script tags or event handler attributes
    Affected if Any stored XSS payloads are found in the plugin configuration data in the WordPress database
  4. Review database for injected scripts
    Query the WordPress database (wp_options table or any custom tables created by the plugin) for script tags, iframe tags, or javascript: URIs in fields related to the Call me Now plugin
    Affected if Malicious scripts or iframes are found stored in plugin-related database records

A user is affected if the Call me Now plugin is installed with version 1.0.5 or lower, or if stored XSS payloads are detected in the plugin settings or database.

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 to the latest patched version of the Call Me Now plugin. Additionally, implement anti-CSRF tokens for state-changing operations and ensure all user-supplied data is properly sanitized on input and encoded on output.

Recommended fix Moderate confidence

Upgrade to a version newer than 1.0.5 (contact vendor for exact patched release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Call me Now' plugin by Tussendoor B.V.
  4. 4. If an update is available, click 'Update Now' to install the latest patched version
  5. 5. Verify the update was successful and the plugin is functioning normally
  6. 6. Test that the CSRF protection is working by confirming nonce/tokens are being validate for admin actions

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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