Skip to main content
mySites.guru
New this monthChecklistsCoreFilestmp Folder ScanDirectAdmin ImportcPanel Quick AddDatabase ChecksStaff Offboarding
CVE-2026-102799MediumCVSS 5.3CVE published 28 October 2026Added to mySites.guru 27 October 2026

iCagenda (com_icagenda) below 4.0.17 (3.9.17 PRO on Joomla 3) - Stored XSS via URL Custom Field and CSV Formula Injection in Registrations Export

JoomliC released iCagenda 4.0.17 (Joomla 4, 5 and 6) and iCagenda PRO 3.9.17 (Joomla 3) on 27 October 2026 to fix two security issues. CVE-2026-102790, rated High by the vendor: the value of a url-type event custom field sent through the front-end event submission form was saved without validation and printed into a link with no escaping and no check on the link scheme, so a submitted event could carry JavaScript that runs in the browser of anyone who views it, including administrators. Submitting needs whatever access level the site gives the submission form, which is Registered by default and anonymous only where the site opened it to Public. CVE-2026-102799, rated Medium: the registrations CSV export did not neutralise cells beginning with = + - or @, so a name, email, note or custom field value entered on the registration form could run as a spreadsheet formula when an administrator opens the export. JoomliC lists 3.2.1 to 4.0.16 as affected by the XSS and 3.5.0 to 4.0.16 by the CSV injection. We confirmed both changes by comparing the public 4.0.16 and 4.0.17 packages. Reported by Akinlabi Omoogun of lulztigre.pw. Not a mySites.guru finding. Both CVE ids are reserved; the CVE records are not yet published. Update to 4.0.17 on Joomla 4, 5 or 6. On Joomla 3, 3.9.17 is available only with an iCagenda PRO subscription, because the free 3.9 line reached end of life on 13 October 2026; the lasting fix is to move the site to Joomla 5 or 6 and iCagenda 4.0.17. Until updated, disable the menu item for front-end event submission and do not open registration exports in a spreadsheet.

Is my site affected?

CVE-2026-102799 is checked by 2 rules. Find the extension and release line your site runs:

ExtensionAffected versionsFixed inWhat to do
iCagendafrom 4.0.0 up to but not including 4.0.174.0.17Update iCagenda to 4.0.17 or later.
iCagendafrom 3.2.1 up to but not including 3.9.173.9.17Update iCagenda to 3.9.17 or later.

How CVE-2026-102799 is scored

The base metrics as Joomla CNA published them, and what each one means for a site running an affected version. Threat and environmental metrics are left out: they describe a moment or a particular install rather than the flaw.

5.3 Medium

CVSS 4.0, scored by Joomla CNA
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:L

How it is reached

AV:N Attack vector
Network. Reachable across the internet
AC:L Attack complexity
Low. Nothing to work around, it just works
AT:N Attack requirements
None. Works against any affected install
PR:L Privileges required
Low. Any logged-in account will do
UI:N User interaction
None. Nobody has to be tricked into anything

What it does to the site

VC:N Confidentiality
None. Nothing can be read
VI:N Integrity
None. Nothing can be altered
VA:N Availability
None. The site stays up

What it does beyond the site

SC:L Confidentiality
Low. Some data on other systems can be read
SI:L Integrity
Low. Some data on other systems can be altered
SA:L Availability
Low. Other systems degrade

The rule below is rated High for the set of 2 CVEs it covers together, not for this record on its own.

Timeline

  1. 27 October 2026mySites.guru check added for iCagenda (from 4.0.0 up to but not including 4.0.17)
  2. 27 October 2026mySites.guru check added for iCagenda (from 3.2.1 up to but not including 3.9.17)
  3. 27 October 2026We published: iCagenda 4.0.17 Fixes a Stored XSS in Event Custom Fields
  4. 28 October 2026CVE-2026-102799 record published by its CNA

Rule details

iCagenda - iCagenda (com_icagenda) below 4.0.17 (3.9.17 PRO on Joomla 3) - Stored XSS via URL Custom Field and CSV Formula Injection in Registrations Export

JoomliC released iCagenda 4.0.17 (Joomla 4, 5 and 6) and iCagenda PRO 3.9.17 (Joomla 3) on 27 October 2026 to fix two security issues. CVE-2026-102790, rated High by the vendor: the value of a url-type event custom field sent through the front-end event submission form was saved without validation and printed into a link with no escaping and no check on the link scheme, so a submitted event could carry JavaScript that runs in the browser of anyone who views it, including administrators. Submitting needs whatever access level the site gives the submission form, which is Registered by default and anonymous only where the site opened it to Public. CVE-2026-102799, rated Medium: the registrations CSV export did not neutralise cells beginning with = + - or @, so a name, email, note or custom field value entered on the registration form could run as a spreadsheet formula when an administrator opens the export. JoomliC lists 3.2.1 to 4.0.16 as affected by the XSS and 3.5.0 to 4.0.16 by the CSV injection. We confirmed both changes by comparing the public 4.0.16 and 4.0.17 packages. Reported by Akinlabi Omoogun of lulztigre.pw. Not a mySites.guru finding. Both CVE ids are reserved; the CVE records are not yet published. Update to 4.0.17 on Joomla 4, 5 or 6. On Joomla 3, 3.9.17 is available only with an iCagenda PRO subscription, because the free 3.9 line reached end of life on 13 October 2026; the lasting fix is to move the site to Joomla 5 or 6 and iCagenda 4.0.17. Until updated, disable the menu item for front-end event submission and do not open registration exports in a spreadsheet.

Affected versions: ≥ 3.2.1 and < 3.9.17

Full advisory: our disclosure post

Our disclosure post

Other vulnerabilities in iCagenda

Updating for CVE-2026-102799 alone can leave a site on a release another rule still matches. These are the other flaws we check for in the same extension.

iCagenda

Latest safe version: 4.0.17

References

CVE-2026-102799 questions

Which versions are affected by CVE-2026-102799?
CVE-2026-102799 is covered by 2 rules: iCagenda from 4.0.0 up to but not including 4.0.17; iCagenda from 3.2.1 up to but not including 3.9.17.
How do I fix CVE-2026-102799?
It depends on the extension and release line your site runs. For iCagenda from 4.0.0 up to but not including 4.0.17: update iCagenda to 4.0.17 or later. For iCagenda from 3.2.1 up to but not including 3.9.17: update iCagenda to 3.9.17 or later.
How severe is CVE-2026-102799?
Joomla CNA scores it 5.3 (Medium) under CVSS 4.0. In plain terms: reachable across the internet, any logged-in account will do and nobody has to be tricked into anything.

Running an affected version on a site you manage?

A free audit tells you which of your Joomla and WordPress sites run an affected version, which are out of date, and which have not been backed up. No card required. If a site is already compromised, fix.mysites.guru is a single fixed fee per incident, usually resolved the same day.

This check is part of the mySites.guru Joomla vulnerability scanner, which reads every installed extension's version on each audit. Browse the rest of the Joomla vulnerability database.

Rules current as of 20 November 2026.