dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-25465

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in codepeople CP Multi View Event Calendar cp-multi-view-calendar allows Stored XSS.This issue affects CP Multi View Event Calendar : from n/a through <= 1.4.36.

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

Stored XSS vulnerability in the CP Multi View Event Calendar plugin allows authenticated attackers to inject malicious JavaScript through unsanitized input fields. The injected payload executes when other users view the affected calendar content.

MitigationUpdate to the latest patched version of the plugin when available. Until then, implement output encoding and input validation on all user-facing fields, or restrict plugin access to trusted users only.

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm plugin installation
    Navigate to WordPress admin dashboard > Plugins, or inspect plugin directory /wp-content/plugins/ for 'cp-multi-view-event-calendar' folder
    Affected if The CP Multi View Event Calendar plugin is present in the WordPress installation
  2. Identify installed version
    Check the plugin header in main PHP file (typically cp-multi-view-event-calendar.php) for 'Version:' tag, or view in WordPress Plugins admin page
    Affected if Installed version matches or precedes any known vulnerable version (version data not provided, compare to latest available)
  3. Verify authenticated access exists
    Review WordPress user roles with access to calendar event creation: go to plugin settings or check capability requirements in plugin code
    Affected if Any user role below Administrator can access calendar/event input forms
  4. Inspect calendar input fields
    Access the calendar event creation interface (typically under plugin menu), view page source or intercept form submission to identify input field names
    Affected if Input fields lack visible output encoding or have known unsanitized parameters (generic check, code review required)
  5. Check for existing malicious payloads
    Query database for stored calendar content: SELECT * FROM wp_posts WHERE post_type LIKE '%calendar%' or relevant custom table, search for <script>, javascript:, or event handler attributes in post_content
    Affected if Stored content contains base64-encoded scripts, event handlers, or suspicious URLs in calendar entries

User is affected if the plugin is installed, an authenticated user with calendar access exists, and unescaped script content is stored in calendar data visible to other users

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 plugin when available. Until then, implement output encoding and input validation on all user-facing fields, or restrict plugin access to trusted users only.

Recommended fix Moderate confidence

Upgrade to the latest available version of CP Multi View Event Calendar (version higher than 1.4.36)

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find 'CP Multi View Event Calendar' (cp-multi-view-calendar)
  5. 5. If an update is available, click 'Update Now'
  6. 6. Alternatively, manually download the latest version from the WordPress Plugin Repository and upload via Plugins > Add New > Upload Plugin
  7. 7. After updating, verify the plugin is functioning correctly
  8. 8. Test that the stored XSS vulnerability is no longer exploitable by attempting to inject a benign script payload in event fields

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-2026-25465 — 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-2026-25465 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