Affected versions: ≥ 1.0.0 and < 5.0.6.1
Full advisory: github.com
CVE-2026-78072HighCVSS 8.7CVE published 28 August 2026Added to mySites.guru 28 August 2026
Sexy Polling Reloaded (com_sexypolling) below 5.0.6.1 (Joomla 3.10 and 4) - Unauthenticated Blind SQL Injection
Sexy Polling Reloaded contains a blind SQL injection that needs no login, no token and no user interaction (CVSS 4.0 vector PR:N, base score 8.7 High), allowing an anonymous visitor to read arbitrary data from the site database. Reported by Krzysztof Zajac of CERT PL. The vendor, Jefferson49, maintains two parallel release lines and shipped the fix to both on 2026-07-25: 5.0.6.1 for the Joomla 3.10 and 4 line, and 5.6.1 for the Joomla 4, 5 and 6 line. Because 5.0.6.1 sorts below 5.6.1, a single rule written to the CVE ceiling of 5.6.1 would wrongly flag the patched legacy build, so this advisory is split into one rule per branch.
Is my site affected?
CVE-2026-78072 is checked by 2 rules. Find the extension and release line your site runs:
| Extension | Affected versions | Fixed in | What to do |
|---|---|---|---|
| Sexy Polling Reloaded | from 1.0.0 up to but not including 5.0.6.1 | 5.0.6.1 | Update Sexy Polling Reloaded to 5.0.6.1 or later. |
| Sexy Polling Reloaded | from 5.1.0 up to but not including 5.6.1 | 5.6.1 | Update Sexy Polling Reloaded to 5.6.1 or later. |
How CVE-2026-78072 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
- 28 August 2026CVE-2026-78072 record published by its CNA
- 28 August 2026mySites.guru check added for Sexy Polling Reloaded (from 1.0.0 up to but not including 5.0.6.1)
- 28 August 2026mySites.guru check added for Sexy Polling Reloaded (from 5.1.0 up to but not including 5.6.1)
Rule details
Sexy Polling Reloaded - Sexy Polling Reloaded (com_sexypolling) 5.1.0 to 5.6.0 (Joomla 4 to 6) - Unauthenticated Blind SQL Injection
Sexy Polling Reloaded contains a blind SQL injection that needs no login, no token and no user interaction (CVSS 4.0 vector PR:N, base score 8.7 High), allowing an anonymous visitor to read arbitrary data from the site database. Reported by Krzysztof Zajac of CERT PL. The vendor, Jefferson49, maintains two parallel release lines and shipped the fix to both on 2026-07-25: 5.0.6.1 for the Joomla 3.10 and 4 line, and 5.6.1 for the Joomla 4, 5 and 6 line. Because 5.0.6.1 sorts below 5.6.1, a single rule written to the CVE ceiling of 5.6.1 would wrongly flag the patched legacy build, so this advisory is split into one rule per branch. If you have updated to 5.6.1, the Joomla backend shows 5.6.1 for every Sexy Polling part, and this warning still says Installed 5.5.x, the cause is a leftover file rather than an unpatched site. At 5.6.x Jefferson49 renamed the extension's XML manifest files and Joomla does not remove the old ones, so an old sexypolling.xml from 5.5.x is still sitting next to the new manifests, and mySites.guru reads the old file first. To clear the warning, delete only these three leftover files: administrator/components/com_sexypolling/sexypolling.xml, plugins/system/sexypolling/sexypolling.xml and plugins/editors-xtd/sexypolling/sexypolling.xml. Keep com_sexypolling.xml, plg_sexypolling.xml and plg_editorbutton.xml in the same folders. The leftovers are old descriptions, not code, so deleting them leaves the site the same as a fresh 5.6.1 install, and the warning clears at the next snapshot.
Affected versions: ≥ 5.1.0 and < 5.6.1
Full advisory: github.com
Other vulnerabilities in Sexy Polling Reloaded
Updating for CVE-2026-78072 alone can leave a site on a release another rule still matches. These are the other flaws we check for in the same extension.
Sexy Polling Reloaded
Latest safe version: 5.6.1
References
- CVE-2026-78072 on cve.org (the official CVE record)
- CVE-2026-78072 in the NIST National Vulnerability Database
- github.com/Jefferson49/Joomla_extension_sexypolling_reloaded
CVE-2026-78072 questions
Which versions are affected by CVE-2026-78072?
CVE-2026-78072 is covered by 2 rules: Sexy Polling Reloaded from 1.0.0 up to but not including 5.0.6.1; Sexy Polling Reloaded from 5.1.0 up to but not including 5.6.1.
How do I fix CVE-2026-78072?
It depends on the extension and release line your site runs. For Sexy Polling Reloaded from 1.0.0 up to but not including 5.0.6.1: update Sexy Polling Reloaded to 5.0.6.1 or later. For Sexy Polling Reloaded from 5.1.0 up to but not including 5.6.1: update Sexy Polling Reloaded to 5.6.1 or later.
How severe is CVE-2026-78072?
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 24 October 2026.