CVE-2025-46510
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in harrysudana Contact Form 7 Calendar cf7-calendar allows Stored XSS.This issue affects Contact Form 7 Calendar: from n/a through <= 3.0.1.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Contact Form 7 Calendar WordPress plugin allows authenticated attackers to inject malicious JavaScript payloads through form submissions. The lack of proper CSRF token validation enables attackers to trick administrators into unknowingly submitting crafted requests that store XSS payloads in the calendar, which then execute when other users view the content.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Contact Form 7 Calendar plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Contact Form 7 Calendar' or check the wp-content/plugins directory for a folder containing 'contact-form-7-calendar'Affected if The plugin is present in the WordPress installation
-
Determine the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find Contact Form 7 Calendar, and note the version number displayed. Alternatively, check the main plugin PHP file for the 'Version' header in the plugin comment blockAffected if The installed version is unpatched (no fixed version was specified in the advisory)
-
Inspect calendar entries for suspicious contentAccess the calendar admin panel and review all events/entries. Look for unusual text, HTML tags, script elements, or encoded payloads in event titles, descriptions, or custom fieldsAffected if Any calendar entry contains JavaScript code, script tags, or unexpected HTML that was not intentionally added by an administrator
-
Review admin action logs for forged form submissionsCheck WordPress activity logs, server access logs, or security plugins for POST requests to calendar submission endpoints originating from unexpected sources or containing anomalous payload patternsAffected if Logs show calendar form submissions with XSS payloads or submissions that bypassed expected CSRF token validation
The environment is affected if the Contact Form 7 Calendar plugin is installed and any calendar entries contain injected JavaScript code or the plugin lacks CSRF token validation for form submissions.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to the latest version of the plugin when available. Until a patch is released, disable the plugin or implement additionalCSRF protection via web application firewall rules. Review admin sessions and look for any unexpected calendar entries.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46510 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-46510 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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