Skip to main content
Menu
CVEs

Hydrogen Calendar Embeds stored XSS in ICS feed event fields

CVE-2026-96771EUVD-2026-131403GHSA-M2QQ-HXW2-HXP5Published November 20, 2026, updated

7.2HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

The Hydrogen Calendar Embeds plugin for WordPress by lbell has a stored DOM-based cross-site scripting flaw in how it handles event fields (SUMMARY, DESCRIPTION, and LOCATION) from ICS feeds. An attacker can exploit it remotely without logging in by injecting scripts into pages that run when a user opens an injected page, but only if they have write access to an ICS feed configured as a calendar source on the site.

Written by a model

Original description

The Hydrogen Calendar Embeds plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via ICS Feed Event Fields (SUMMARY/DESCRIPTION/LOCATION) in all versions up to, and including, 3.0.3 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 the attacker to have write access to an ICS feed that has been configured as a calendar source on the target WordPress site.

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-96771 (Hydrogen Calendar Embeds <= 3.0.3 - Unauthenticated Stored DOM-Based Cross-Site Scripting via ICS Feed Event Fields…), 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-96771 (entry last updated 2026-11-20):
Affected:
- lbell Hydrogen Calendar Embeds: through 3.0.3
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-96771 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-96771 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/4a4ead0a-29ca-46c4-a38d-90e5684b4c54?source=cve
- https://plugins.trac.wordpress.org/browser/hydrogen-calendar-embeds/tags/3.0.3/public/js/tippy.js#L88
- https://plugins.trac.wordpress.org/browser/hydrogen-calendar-embeds/tags/3.0.3/public/js/tippy.js#L116
- https://plugins.trac.wordpress.org/browser/hydrogen-calendar-embeds/tags/3.0.3/public/js/tippy.js#L60
- https://plugins.trac.wordpress.org/browser/hydrogen-calendar-embeds/tags/3.0.3/public/js/tippy.js#L196
- https://plugins.trac.wordpress.org/browser/hydrogen-calendar-embeds/tags/3.0.3/includes/class-hycal-ics-proxy.php#L327
- https://plugins.trac.wordpress.org/browser/hydrogen-calendar-embeds/tags/3.0.3/includes/class-hycal-ics-proxy.php#L428
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3763970%40hydrogen-calendar-embeds&new=3763970%40hydrogen-calendar-embeds
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-96771
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-96771"}.

Affected versions

cve.now Index

32Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.2/10CVSS 7.2
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 77 if added to CISA KEV
  • Would score about 72 if CISA's SSVC rates exploitation active
  • Would score about 37 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Evidence 10

Questions about CVE-2026-96771

Is CVE-2026-96771 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-96771?

Hydrogen Calendar Embeds: through 3.0.3.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.