CVE-2026-110701 codepeople CVE debrief

Who should care

Defenders responsible for WordPress installations with the CP Multi View Events Calendar plugin should assess exposure and prioritize verification and remediation efforts. This includes reviewing plugin versions, restricting access to plugin settings, and monitoring for potential XSS attacks. Security teams and vulnerability management teams should also be aware of the potential impact and take necessary actions to protect their environments.

Why it matters

The CP Multi View Events Calendar plugin for WordPress is vulnerable to Stored Cross-Site Scripting, allowing unauthenticated attackers to inject arbitrary web scripts. Defenders should prioritize verification and remediation to prevent potential XSS attacks.

• Unauthenticated attackers may inject arbitrary web scripts
• Injected scripts may execute on user-accessed pages
• Defenders must verify and update the plugin to prevent potential XSS attacks
• Remediation priority is high due to the CVSS score of 7.2

Technical summary

The CP Multi View Events Calendar plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'CalendarTitle' parameter in all versions up to, and including, 1.4.42. This vulnerability is caused by insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject arbitrary web scripts. These scripts can execute on user-accessed pages, potentially leading to unauthorized actions and data breaches. The vulnerability's CVSS score of 7.2 indicates a high severity level, emphasizing the need for prompt verification and remediation.

Defensive priority

Defenders should prioritize verifying and updating the CP Multi View Events Calendar plugin to prevent potential XSS attacks.

Recommended defensive actions

• Verify and update the CP Multi View Events Calendar plugin to the latest version
• Review and restrict access to the plugin's settings and functionality
• Monitor for potential XSS attacks and anomalies
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its CVSS score and vector. The vulnerability is confirmed in versions up to 1.4.42 of the CP Multi View Events Calendar plugin. Evidence is based on the CVE Program record and NVD entry, which detail the vulnerability's impact and affected versions. Defenders should verify the plugin version and review the official advisory for specific guidance on remediation.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.