# CVE-2026-119714: My Calendar 3.8.8 before 3.8.11 Unauthenticated Shortcode Injection via mcs Parameter


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 30 Oct 2026
- **Also known as:** GHSA-j2m8-rg5v-vvqc

## What is CVE-2026-119714?

CVE-2026-119714 is a medium-severity vulnerability in joedolson My Calendar - Accessible Event Manager, published on 30 Oct 2026. 

### Official description

My Calendar WordPress plugin 3.8.8 before 3.8.11 contains a shortcode injection vulnerability that allows unauthenticated attackers to execute registered shortcodes via the mcs search parameter. The mcs value reaches mc_search_results() in src/my-calendar-search.php without bracket encoding before do_shortcode runs, so a GET request triggers shortcodes on any page or post, enabling content injection and spoofing.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-119714?


## How do I fix CVE-2026-119714?

No fix has been published for CVE-2026-119714 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119714 being exploited?

There is no known exploitation of CVE-2026-119714 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119714 and fix it if it is affected.

What it is: CVE-2026-119714 is a medium-severity vulnerability in joedolson My Calendar - Accessible Event Manager, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119714 in the wild and no public exploit code.

Affected product: joedolson My Calendar - Accessible Event Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119714/ (Markdown: https://insights.sbomify.com/CVE-2026-119714/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119714
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119714
- OSV: https://osv.dev/vulnerability/CVE-2026-119714

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119714/
Summaries are generated and may contain mistakes; the official description above is the record.