Skip to main content
mySites.guru
CriticalA PHP security release fixes two CVSS 9.2 flaws, and PHP 8.1 and older get no patchWhat it means for your site

iCagenda security vulnerabilities

mySites.guru tracks 3 vulnerabilities in iCagenda (com_icagenda), covering 5 CVEs. Every connected Joomla site is checked against them on each audit.

Is my site affected?

Your site is affected if it runs iCagenda in any of these ranges:

  • from 4.0.8 up to but not including 4.0.12
  • from 4.0.0 up to but not including 4.0.8
  • from 3.2.1 up to but not including 3.9.15
Latest safe version
4.0.12 or later. No rule we check matches that release or any newer one.
What to do
Update iCagenda to 4.0.12 or later from the vendor, then confirm the installed version on the Joomla administrator's Extensions: Manage screen.

Every iCagenda vulnerability we track

Newest first. CVSS is the score published in each CVE record, where it has one; the severity column is the rating our check uses.

CVEAffected versionsFixed inSeverityAdded
CVE-2026-48939CVSS 10.0from 4.0.0 up to but not including 4.0.84.0.8Critical2026-06-15
CVE-2026-48939CVSS 10.0from 3.2.1 up to but not including 3.9.153.9.15Critical2026-06-15
CVE-2026-67365CVSS 9.2CVE-2026-71571CVSS 8.6CVE-2026-67366CVSS 5.3CVE-2026-71570CVSS 5.1from 4.0.8 up to but not including 4.0.124.0.12Unrated-

What we check for

CriticalCVE-2026-489392026-06-15

iCagenda (com_icagenda) below 4.0.8 - Unauthenticated Arbitrary File Upload (RCE) (CVE-2026-48939, CISA KEV)

iCagenda's frontend "Submit an Event" form (index.php?option=com_icagenda&task=submit.submit) accepts arbitrary file uploads with no server-side type check. The submitAccess access-level setting is enforced only in the view, not on the processing path, so a guest with a freely-harvested CSRF token can upload a .php web shell to a web-served, predictable path and execute it, effectively unauthenticated RCE. Confirmed exploited in the wild from 15 Jun 2026 (icagenda-batch/1.0 scanner). CVE-2026-48939, added to the CISA Known Exploited Vulnerabilities catalog on 10 Jul 2026. Fixed in 4.0.8 (JoomliC Critical Security Release, 15 Jun 2026); update immediately. If you cannot patch, rename the com_icagenda component folders, since unpublishing does not close the hole.

Affected versions: ≥ 4.0.0 and < 4.0.8

Full advisory: www.cve.org

CriticalCVE-2026-489392026-06-15

iCagenda (com_icagenda) below 4.0.8 - Unauthenticated Arbitrary File Upload (RCE) (CVE-2026-48939, CISA KEV)

iCagenda's frontend "Submit an Event" form (index.php?option=com_icagenda&task=submit.submit) accepts arbitrary file uploads with no server-side type check. The submitAccess access-level setting is enforced only in the view, not on the processing path, so a guest with a freely-harvested CSRF token can upload a .php web shell to a web-served, predictable path and execute it, effectively unauthenticated RCE. Confirmed exploited in the wild from 15 Jun 2026 (icagenda-batch/1.0 scanner). CVE-2026-48939, added to the CISA Known Exploited Vulnerabilities catalog on 10 Jul 2026. Fixed in 4.0.8 (JoomliC Critical Security Release, 15 Jun 2026); update immediately. If you cannot patch, rename the com_icagenda component folders, since unpublishing does not close the hole.

Affected versions: ≥ 3.2.1 and < 3.9.15

Full advisory: our disclosure post

iCagenda (com_icagenda) 4.0.8 to 4.0.11 - Unauthenticated SQL Injection (CVE-2026-67365)

iCagenda 4.0.8 through 4.0.11 (the Joomla 4/5/6 branch) contain an unauthenticated SQL injection in mod_icagenda_calendar, reachable through com_ajax with no session, token or account (CVE-2026-67365, CVSS 4.0 9.2 Critical). An anonymous visitor can read arbitrary database contents including Joomla user password hashes. This is a separate flaw from the earlier CVE-2026-48939 file upload RCE and was reported by Joep van Antwerpen of Onvio. Fixed in 4.0.12; update to 4.0.13 or later, which also fixes a stored XSS regression introduced in 4.0.8. The legacy Joomla 3 branch (3.9.x) is not affected by this SQL injection.

Affected versions: ≥ 4.0.8 and < 4.0.12

Full advisory: www.icagenda.com

Timeline

  1. 15 June 2026Check added for CVE-2026-48939 (from 4.0.0 up to but not including 4.0.8)
  2. 15 June 2026Check added for CVE-2026-48939 (from 3.2.1 up to but not including 3.9.15)
  3. 15 June 2026We published: Zero Day Vulnerability Found in iCagenda Joomla Extension
  4. 20 June 2026CVE-2026-48939 record published
  5. 14 August 2026CVE-2026-67365 record published
  6. 14 August 2026CVE-2026-71571 record published
  7. 14 August 2026CVE-2026-67366 record published
  8. 14 August 2026CVE-2026-71570 record published
  9. 17 August 2026We published: iCagenda 4.0.12 fixes an unauthenticated SQL injection

What we have written about iCagenda

References

Each CVE page above links its official cve.org record and its NVD entry.

iCagenda vulnerability questions

Which versions of iCagenda are vulnerable?
mySites.guru tracks 3 vulnerabilities in iCagenda (com_icagenda). A site is affected if its installed version is in any of these ranges: from 4.0.8 up to but not including 4.0.12; from 4.0.0 up to but not including 4.0.8; from 3.2.1 up to but not including 3.9.15.
What is the latest safe version of iCagenda?
4.0.12. Every vulnerability tracked here is fixed by 4.0.12, and no rule we check matches that release or any later one.
How do I check which version of iCagenda my Joomla site runs?
The installed version is listed on the Joomla administrator's Extensions: Manage screen; search it for com_icagenda. mySites.guru reads the installed version on every audit of a connected site and checks it against these rules.

Running iCagenda 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.

CVE identifiers: CVE-2026-48939, CVE-2026-67365, CVE-2026-71571, CVE-2026-67366, CVE-2026-71570. Rules current as of 24 October 2026.