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

CVE-2025-32597

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 George Sexton WordPress Events Calendar Plugin – connectDaily connect-daily-web-calendar allows Cross-Site Scripting (XSS).This issue affects WordPress Events Calendar Plugin – connectDaily: from n/a through <= 1.5.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

A CSRF vulnerability in the connectDaily WordPress Events Calendar plugin (versions <= 1.5.4) allows attackers to trick authenticated administrators into performing unintended actions that inject malicious XSS payloads. When successfully exploited, arbitrary JavaScript can execute in the browsers of users viewing the affected calendar content.

MitigationUpdate connectDaily plugin to the latest version immediately. If no patch is available, disable the plugin. Additionally, implement anti-CSRF tokens on state-changing forms and validate/sanitize all user inputs server-side.

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 connectDaily plugin installation and version
    Check the installed version by looking in WordPress admin under Plugins > Installed Plugins, or inspect the plugin main file header in wp-content/plugins/connect-daily-events-calendar/ for the 'Version' comment. Compare against affected versions <= 1.5.4.
    Affected if connectDaily plugin is installed and version is 1.5.4 or lower.
  2. Confirm plugin is active
    In WordPress admin, verify that the connectDaily plugin shows as 'Active' on the Plugins page. Only active plugins can be exploited.
    Affected if The connectDaily plugin is active on the WordPress site.
  3. Inspect calendar event data for XSS payloads
    Navigate to the connectDaily events calendar section in WP admin and review existing calendar events, or query the WordPress database tables where calendar data is stored (often wp_options or custom tables). Look for suspicious script tags, javascript: URLs, or encoded payloads in event titles, descriptions, or location fields.
    Affected if Malicious XSS payloads are present in any calendar event data or settings.
  4. Review recent admin action logs for suspicious modifications
    Check WordPress activity logs, server access logs, or any audit trail for recent POST requests to admin-ajax.php or admin.php involving connectDaily endpoints that may have injected XSS content without proper CSRF validation.
    Affected if There are records of unauthorized calendar modifications or unexpected admin actions related to the plugin.
  5. Test for missing CSRF protection on forms
    Inspect the HTML source of any connectDaily admin forms (event creation/editing, calendar settings) and verify whether anti-CSRF tokens (wpnonce fields) are present in the form markup. Missing nonce fields indicate vulnerability to the CSRF attack vector.
    Affected if connectDaily admin forms lack CSRF token/nonce validation.

You are affected if the connectDaily plugin version is 1.5.4 or lower and the plugin is active, regardless of whether XSS payload injection has already occurred.

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 connectDaily plugin to the latest version immediately. If no patch is available, disable the plugin. Additionally, implement anti-CSRF tokens on state-changing forms and validate/sanitize all user inputs server-side.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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