CVE-2026-110701: CP Multi View Events Calendar <= 1.4.42 - Unauthenticated Stored Cross-Site Scripting via 'CalendarTitle' Parameter

Q: Which installations are exposed to unauthenticated exploitation?

Installations running version 1.4.42 or earlier are exposed only if an administrator enabled the "Allow edition in frontend?" option on at least one calendar view. That setting exposes an unauthenticated add endpoint and a publicly accessible nonce.

Q: What does an attacker need to exploit this issue?

An attacker does not need authentication or user interaction to submit the malicious CalendarTitle value when the required frontend-editing setting is enabled. The injected script executes later when someone accesses the affected page.

Q: What can be done while patching is unavailable?

Disable "Allow edition in frontend?" on every calendar view to remove the condition that exposes the unauthenticated add endpoint and public nonce.

Q: How can administrators assess whether their site may already be affected?

Review calendar content and pages that display calendars for unexpected or malicious CalendarTitle values, especially where frontend editing was enabled. Any stored injected value may execute in a visitor's browser when the associated page is viewed.

Published Oct 16, 2026

Updated

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 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires that an administrator has enabled the "Allow edition in frontend?" option on at least one calendar view, which exposes the unauthenticated add endpoint and a publicly accessible nonce.

Affected Software

1 affected component

CodePeople CP Multi View Events Calendar<=1.4.42

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Configuration
Disable the "Allow edition in frontend?" option on all calendar views to prevent exposure of the unauthenticated add endpoint.
CP Multi View Events Calendar Allow edition in frontend? = disabled

Event History

Oct 16, 2026

CVE Published

via MITRE·06:41 AM

Data Sourced

via MITRE·06:41 AM

DescriptionSeverityWeakness

Frequently Asked Questions

Which installations are exposed to unauthenticated exploitation?

Installations running version 1.4.42 or earlier are exposed only if an administrator enabled the "Allow edition in frontend?" option on at least one calendar view. That setting exposes an unauthenticated add endpoint and a publicly accessible nonce.

What does an attacker need to exploit this issue?

An attacker does not need authentication or user interaction to submit the malicious CalendarTitle value when the required frontend-editing setting is enabled. The injected script executes later when someone accesses the affected page.

What can be done while patching is unavailable?

Disable "Allow edition in frontend?" on every calendar view to remove the condition that exposes the unauthenticated add endpoint and public nonce.

How can administrators assess whether their site may already be affected?

Review calendar content and pages that display calendars for unexpected or malicious CalendarTitle values, especially where frontend editing was enabled. Any stored injected value may execute in a visitor's browser when the associated page is viewed.

CVE-2026-110701: CP Multi View Events Calendar <= 1.4.42 - Unauthenticated Stored Cross-Site Scripting via 'CalendarTitle' Parameter

Affected Software

Remediation

Event History

Frequently Asked Questions

Which installations are exposed to unauthenticated exploitation?

What does an attacker need to exploit this issue?

What can be done while patching is unavailable?

How can administrators assess whether their site may already be affected?

Company

Resources

Contact

Frequently Asked Questions

Which installations are exposed to unauthenticated exploitation?

What does an attacker need to exploit this issue?

What can be done while patching is unavailable?

How can administrators assess whether their site may already be affected?