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

CVE-2025-58861

HIGH · 7.1 CVSS v3.1 Published 2025-09-05
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 WP Corner Quick Event Calendar quick-event-calendar allows Stored XSS.This issue affects Quick Event Calendar: from n/a through <= 1.4.9.

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

The WP Corner Quick Event Calendar plugin before version 1.4.10 is vulnerable to CSRF attacks that allow Stored XSS. Attackers can trick authenticated administrators into submitting malicious requests that inject JavaScript payloads into event calendar data. When other users view the calendar, the stored XSS executes in their browsers.

MitigationUpgrade to Quick Event Calendar version 1.4.10 or later. Until then, enforce admin session isolation and warn administrators not to click untrusted links.

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. Locate the plugin version file
    Access your WordPress installation via file manager or FTP, navigate to /wp-content/plugins/quick-event-calendar/ and open the main plugin file (commonly named quick-event-calendar.php or similar) to find the version declaration in the plugin header comment
    Affected if The version number displayed is lower than 1.4.10 (for example, 1.4.9, 1.4.8, etc.)
  2. Verify the plugin is active
    Log into the WordPress admin dashboard, go to Plugins > Installed Plugins, and confirm that Quick Event Calendar is currently activated
    Affected if The plugin shows as Active in the WordPress admin plugin list
  3. Inspect calendar event data for malicious scripts
    Access your WordPress database via phpMyAdmin or command line, query the plugin's custom table (commonly named weq_events or similar under the WordPress prefix) and examine the event_title, event_description, or similar text fields for any <script> tags, javascript: URIs, or on* event handlers
    Affected if Any event records contain suspicious JavaScript code patterns such as <script>, event handlers like onload or onerror, or encoded payloads that could execute in a browser
  4. Review recent admin activity logs
    Check WordPress activity logs, server access logs, or security plugins for any unusual POST requests to the calendar admin endpoints that may have been triggered via CSRF
    Affected if There are logged admin actions creating or modifying calendar events that you do not recognize or did not intentionally perform

You are affected if the Quick Event Calendar plugin is installed with a version earlier than 1.4.10 AND the plugin is currently active in your WordPress environment.

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

Upgrade to Quick Event Calendar version 1.4.10 or later. Until then, enforce admin session isolation and warn administrators not to click untrusted links.

Recommended fix Moderate confidence

1.5.0 or later (verify the latest version in the WordPress plugin repository)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Quick Event Calendar' plugin (by WP Corner)
  4. 4. Check if an update is available and update to the latest version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository or the vendor's website and reinstall

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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