My Calendar stored cross-site scripting in event titles
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The My Calendar – Accessible Event Manager plugin for WordPress has a stored cross-site scripting flaw in its event title field. A remote attacker with a low-privilege login, such as a subscriber account, can save a malicious script as an event title, which then runs in the browsers of visitors who view that event on the public calendar.
Written by a model
Original description
The My Calendar – Accessible Event Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'event_title' 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 the plugin's documented permission grant to be applied, which allows Subscriber-level users to add and publish events; once granted, a self-submitted event title containing an entity-encoded payload is auto-published and fires in any visitor's browser upon clicking the event on the public calendar.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-118055 (My Calendar <= 3.8.13 - Authenticated (Subscriber+) Stored Cross-Site Scripting via Event Title), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-118055 (entry last updated 2026-11-20):
Affected:
- joedolson My Calendar – Accessible Event Manager: through 3.8.13
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-118055 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-118055 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/15e7d812-d472-4be4-a33a-581b77d1cbfa?source=cve
- https://plugins.trac.wordpress.org/browser/my-calendar/tags/3.8.11/my-calendar-output.php#L467
- https://plugins.trac.wordpress.org/browser/my-calendar/tags/3.8.11/js/modal/accessible-modal-window-aria.js#L252
- https://plugins.trac.wordpress.org/browser/my-calendar/tags/3.8.11/my-calendar-event-editor.php#L511
- https://plugins.trac.wordpress.org/browser/my-calendar/tags/3.8.11/my-calendar-event-editor.php#L2402
- https://plugins.trac.wordpress.org/browser/my-calendar/tags/3.8.11/includes/kses.php#L46
- https://github.com/joedolson/my-calendar/compare/v3.8.13...v3.8.14
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-118055
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-118055"}.Affected versions
- joedolson My Calendar – Accessible Event Managerthrough 3.8.13
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.4/10CVSS 6.4
- No patch5/5No patch listed yet
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 9
Questions about CVE-2026-118055
Is CVE-2026-118055 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-118055?
My Calendar – Accessible Event Manager: through 3.8.13.
Source: cve.now feed data
Related
- CVE-2026-104798My Calendar <= 3.8.7 - Unauthenticated Privilege Escalation to 'mcs' Parameter via Reflected Shortcode Injection into 'above' Attribute
- CVE-2026-6854My Calendar <= 3.7.8 - Unauthenticated SQL Injection via 'mc_auth' and 'mc_host' Parameters
- CVE-2026-120117My Calendar <= 3.8.13 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'event_street' Address Field
- CVE-2026-121538My Calendar <= 3.8.13 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'event_post' Parameter
- CVE-2026-119088My Calendar <= 3.8.13 - Authenticated (Subscriber+) Stored Cross-Site Scripting via Event Title
- CVE-2026-77187My Calendar <= 3.8.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'before' and 'after' Shortcode Attributes
No corrections so far. Something wrong on this page? Report an error.