Affected versions: ≥ 9.0.0 and < 10.11.2
Full advisory: our disclosure post
CVE-2026-57831HighCVSS 8.7CVE published 15 July 2026Added to mySites.guru 13 July 2026
DPCalendar (com_dpcalendar) 9.0 to 10.11.1 (Joomla 4 to 6) - Unauthenticated Blind SQL Injection
DPCalendar on the Joomla 4 to 6 line (9.x and 10.x) contains an unauthenticated blind SQL injection in the front-end events model. The filter_created_by request parameter is placed into the events query without an integer cast (site EventsModel::getListQuery), so an anonymous visitor can inject boolean conditions and read arbitrary database contents including user password hashes and the Joomla secret through the public events feed at index.php?option=com_dpcalendar&view=events&format=raw. No login, token or CSRF is required. It is a read-only injection (no write or RCE). All editions (Free, Pro, Business) share the vulnerable site model. The flaw dates to 8.18.0 and affects every current-line release up to and including 10.11.0. Fixed in 10.11.2, which integer-casts the author filter. Update to 10.11.2 or later; on the 9.x line the upgrade path is 9.x to 10.0.0, then 10.6.0, then 10.11.2. Joomla 3 (8.x) sites are handled by a separate rule (fixed in 8.19.4). Temporary mitigation: block non-numeric filter_created_by at the WAF, or unpublish DPCalendar front-end menu items. Discovered and reported by mySites.guru.
Is my site affected?
CVE-2026-57831 is checked by 2 rules. Find the extension and release line your site runs:
| Extension | Affected versions | Fixed in | What to do |
|---|---|---|---|
| DPCalendar | from 9.0.0 up to but not including 10.11.2 | 10.11.2 | Update DPCalendar to 10.11.2 for this flaw, or to 10.12.1 or later, which no rule we check matches. |
| DPCalendar | from 8.18.0 up to but not including 8.19.4 | 8.19.4 | Update DPCalendar to 8.19.4 for this flaw, or to 10.12.1 or later, which no rule we check matches. |
How CVE-2026-57831 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.7 High
CVSS 4.0, scored by Joomla CNACVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NHow 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:N Privileges required
- None. No account needed
- 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:N Integrity
- None. Nothing can be altered
- VA:N Availability
- None. The site stays up
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
Timeline
- 13 July 2026mySites.guru check added for DPCalendar (from 9.0.0 up to but not including 10.11.2)
- 13 July 2026mySites.guru check added for DPCalendar (from 8.18.0 up to but not including 8.19.4)
- 13 July 2026We published: Unauthenticated SQL Injection in DPCalendar found by mySites.guru
- 15 July 2026CVE-2026-57831 record published by its CNA
Rule details
DPCalendar - DPCalendar (com_dpcalendar) 8.18.0 to 8.19.3 (Joomla 3) - Unauthenticated Blind SQL Injection
DPCalendar on the Joomla 3 (8.x) branch contains an unauthenticated blind SQL injection in the front-end events model. The filter_created_by request parameter is placed into the events query without an integer cast (site EventsModel::getListQuery), so an anonymous visitor can inject boolean conditions and read arbitrary database contents including user password hashes and the Joomla secret through the public events feed at index.php?option=com_dpcalendar&view=events&format=raw. No login, token or CSRF is required. It is a read-only injection (no write or RCE). All editions (Free, Pro, Business) share the vulnerable site model. The flaw was introduced in 8.18.0 and affects every 8.x release from 8.18.0 up to 8.19.3. Fixed in 8.19.4, which integer-casts the author filter. Update to 8.19.4 or later, or migrate to Joomla 4 to 6 and DPCalendar 10.11.2. Joomla 4 to 6 (9.x and 10.x) sites are handled by a separate rule (fixed in 10.11.2). Temporary mitigation: block non-numeric filter_created_by at the WAF, or unpublish DPCalendar front-end menu items. Discovered and reported by mySites.guru.
Affected versions: ≥ 8.18.0 and < 8.19.4
Full advisory: our disclosure post
Our disclosure post
Other vulnerabilities in DPCalendar
Updating for CVE-2026-57831 alone can leave a site on a release another rule still matches. These are the other flaws we check for in the same extension.
DPCalendar
Latest safe version: 10.12.1
- CVE-2026-78071 High, from 7.0.0 up to but not including 8.19.6
- CVE-2026-78070 Medium, from 5.5.0 up to but not including 8.19.5
- CVE-2024-21727 Medium, from 8.0.0 up to and including 8.14.0
References
- CVE-2026-57831 on cve.org (the official CVE record)
- CVE-2026-57831 in the NIST National Vulnerability Database
- Unauthenticated SQL Injection in DPCalendar found by mySites.guru
CVE-2026-57831 questions
Which versions are affected by CVE-2026-57831?
CVE-2026-57831 is covered by 2 rules: DPCalendar from 9.0.0 up to but not including 10.11.2; DPCalendar from 8.18.0 up to but not including 8.19.4.
How do I fix CVE-2026-57831?
It depends on the extension and release line your site runs. For DPCalendar from 9.0.0 up to but not including 10.11.2: update DPCalendar to 10.11.2 for this flaw, or to 10.12.1 or later, which no rule we check matches. For DPCalendar from 8.18.0 up to but not including 8.19.4: update DPCalendar to 8.19.4 for this flaw, or to 10.12.1 or later, which no rule we check matches.
How severe is CVE-2026-57831?
Joomla CNA scores it 8.7 (High) under CVSS 4.0. In plain terms: reachable across the internet, no account needed 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 5 October 2026.