My Calendar <= 3.8.13 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'event_post' Parameter
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| joedolson | My Calendar – Accessible Event Manager | unaffected |
|
No data.
No data.
No data available yet.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The My Calendar – Accessible Event Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'event_post (post ID) + event_title (XSS payload) + content (shortcode)' parameter in all versions up to, and including, 3.8.13 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires an administrator to have granted the mc_add_events capability to Subscriber-level or other lower-privileged roles, which is the plugin's documented workflow for allowing front-end event submissions. | |
| Title | My Calendar <= 3.8.13 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'event_post' Parameter | |
| Weaknesses | CWE-79 | |
| References |
|
|
| Metrics |
cvssV3_1
|
No data.
No data.
No data.
No data.
No data.