Skip to main content
mySites.guru
Free Audit
NewAdd every Joomla and WordPress site on a WHM or cPanel server in one goSee how it works
CVE-2026-71571HighCVSS 8.6CVE published 14 August 2026Added to mySites.guru 14 August 2026

iCagenda (com_icagenda) 4.0.8 to 4.0.11 - Unauthenticated SQL Injection (CVE-2026-67365), Authenticated SQL Injection, CSRF on Registration Actions and ACL Bypass User Enumeration

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. Three further iCagenda CVEs published the same day are fixed in the same 4.0.12 release: CVE-2026-71571 (CVSS 4.0 8.6 High), an SQL injection through an unescaped numeric filter reachable by backend users with access to iCagenda; CVE-2026-67366 (5.3 Medium), missing CSRF token checks on several state-changing front-end registration actions; and CVE-2026-71570 (5.1 Medium), an ACL bypass that lets a backend operator scoped to com_icagenda enumerate Joomla user profiles.

Is my site affected?

Affected
iCagenda from 4.0.8 up to but not including 4.0.12
Fixed in
4.0.12
What to do
Update iCagenda to 4.0.12 for this flaw, or to 4.0.17 or later, which no rule we check matches.
Check whether your sites are affected

How CVE-2026-71571 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.

8.6 High

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

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:H Privileges required
High. Needs an account with elevated rights
UI:N User interaction
None. Nobody has to be tricked into anything

What it does to the site

VC:H Confidentiality
High. Everything the site holds can be read
VI:H Integrity
High. Data and files can be altered at will
VA:H Availability
High. The site can be taken down

What it does beyond the site

SC:N Confidentiality
None. Other systems keep their data
SI:N Integrity
None. Other systems keep their integrity
SA:N Availability
None. Other systems stay up

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

Timeline

  1. 14 August 2026CVE-2026-71571 record published by its CNA
  2. 14 August 2026mySites.guru check added for iCagenda (from 4.0.8 up to but not including 4.0.12)

Rule details

Other vulnerabilities in iCagenda

Updating for CVE-2026-71571 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-71571 questions

Which versions are affected by CVE-2026-71571?
CVE-2026-71571 affects iCagenda from 4.0.8 up to but not including 4.0.12. The fix is in 4.0.12.
How do I fix CVE-2026-71571?
Update iCagenda to 4.0.12 for this flaw, or to 4.0.17 or later, which no rule we check matches. Then confirm the installed version on the Joomla administrator's Extensions: Manage screen.
How severe is CVE-2026-71571?
Joomla CNA scores it 8.6 (High) under CVSS 4.0. In plain terms: reachable across the internet, needs an account with elevated rights 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 11 November 2026.