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

CVE-2025-59131

HIGH · 7.1 CVSS v3.1 Published 2025-12-30
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 hoernerfranz WP-CalDav2ICS wp-caldav2ics allows Stored XSS.This issue affects WP-CalDav2ICS: from n/a through <= 1.3.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 · high confidence

A CSRF vulnerability in the WP-CalDav2ICS WordPress plugin (versions up to 1.3.4) allows authenticated administrators to be tricked into performing unintended actions that store malicious JavaScript payloads. Since the XSS is stored, the injected script executes each time administrators or other users view the affected content, potentially compromising admin sessions and leading to further privilege escalation.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing operations and sanitize all user-supplied data before storage and output to prevent XSS. WordPress nonces and output escaping functions should be applied throughout the plugin.

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. Identify WP-CalDav2ICS plugin version
    Log into the WordPress admin panel, navigate to Plugins > Installed Plugins, locate WP-CalDav2ICS, and note the version number displayed
    Affected if The installed version is 1.3.4 or any lower version number
  2. Confirm plugin is active
    In the same plugins list, verify that WP-CalDav2ICS shows as Active rather than Inactive or Network Inactive
    Affected if The plugin is currently active and processing requests
  3. Inspect plugin settings for stored scripts
    Access the plugin settings page (usually under Settings or a dedicated WP-CalDav2ICS menu), examine any text fields, calendars, or content storage areas for unexpected script tags, img onerror attributes, or javascript: URIs
    Affected if Any field contains raw script tags or event handlers like onclick, onerror, onload
  4. Review WordPress database for malicious entries
    If database access is available, query the wp_postmeta and wp_options tables for the plugin prefix/keys, looking for serialized or plain text entries containing <script, javascript:, or event handler patterns
    Affected if Suspicious JavaScript payloads are found stored in plugin-related database entries
  5. Check browser console for XSS indicators
    As an administrator, visit pages that display plugin-generated content (calendars, exported ICS files viewed in admin, settings pages), then open browser developer tools and inspect the console for any script execution errors or loaded payloads
    Affected if Injected scripts execute when viewing plugin-managed content

You are affected if WP-CalDav2ICS version 1.3.4 or lower is installed and active, and any stored content from this plugin contains unsanitized JavaScript that could execute in admin sessions

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

Implement anti-CSRF tokens (nonces) on all state-changing operations and sanitize all user-supplied data before storage and output to prevent XSS. WordPress nonces and output escaping functions should be applied throughout the plugin.

Recommended fix Moderate confidence

Latest version of WP-CalDav2ICS (greater than 1.3.4)

  1. 1. Check the WP-CalDav2ICS plugin settings page for any available updates
  2. 2. Navigate to Plugins > All Plugins in WordPress admin dashboard
  3. 3. Update WP-CalDav2ICS to the latest available version
  4. 4. Verify the update was successful and the plugin is functioning correctly
  5. 5. Consider implementing additional CSRF protections via WordPress security plugins or server-side token validation

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
  • 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-59131 — 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-59131 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