# CVE-2026-102790: Joomla Extension - icagenda.com -  Authenticated Stored XSS in iCagenda 4.0.8 to 4.0.12

Status: published. Published: 2026-10-28. Updated: 2026-11-06.

Joomla Extension - icagenda.com -  Stored XSS via url-type event Custom Field in iCagenda 3.2.1 to 4.0.16

## Remediation

No remediation reported in collected sources

## Affected products and versions

- icagenda.com / iCagenda extension for Joomla: 3.2.1-4.0.16 (affected). Source: CNA: Joomla

## Severity and prioritization

- CVSS 4.0: 8.6 (high); CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N; source: CNA: Joomla

- CISA KEV: No listing in collected sources

- EPSS: 0.28% as of 2026-11-06; percentile 20.99%

- SSVC: exploitation none; automatable no; technical impact total; source ADP: CISA-ADP

- Weaknesses: CWE-79

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://www.icagenda.com/ (CNA: Joomla; product)

## Provenance

- CNA: Joomla: https://www.cve.org/CVERecord?id=CVE-2026-102790; retrieved 2026-11-06; source updated 2026-11-06

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-102790; retrieved 2026-11-06; source updated Not reported

Revision: e7fb33c679619dc15e658343db22294df9df098ac098ea1420e0f55dd0f6a69e

Canonical: https://y2.dev/cve/CVE-2026-102790

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.