Skip to main content
mySites.guru
J!Awards 2026mySites.guru is shortlisted for Your Favourite Tool in Your Joomla WorkflowVote by 11 OctoberHow to vote
CVE-2026-56292CriticalCVSS 9.2CVE published 9 July 2026Added to mySites.guru 9 July 2026

AcyMailing (com_acym) below 10.11.1 - Unauthenticated SQL Injection

CVE-2026-56292. AcyMailing for Joomla is affected by an unauthenticated SQL injection in a public front-end endpoint. Request parameters were placed into the column list of a SELECT query without sanitising or quoting them (Joomla's text filter strips HTML but does not neutralise SQL syntax), letting an anonymous visitor read data from any table in the site database, including Joomla user accounts and password hashes. No login, account or CSRF token is required. Discovered and responsibly reported to Acyba by mySites.guru (Phil Taylor); fixed in AcyMailing 10.11.1 (released 9 July 2026). A web application firewall that filters SQL (Cloudflare managed rules, Admin Tools, RSFirewall) blocks the payload as mitigation, but the only reliable fix is to update. Update every affected site to 10.11.1 or later. Also covered by this rule: CVE-2023-39970 (unrestricted file upload, RCE), CVE-2023-39971 (XSS), CVE-2023-39972 (unauthorised mailing list creation), CVE-2023-39973 (unauthorised removal of campaign attachments) and CVE-2023-39974 (subscriber count disclosure), all affecting AcyMailing 6.7.0 to 8.6.3. Also within this rule: CVE-2023-28731, CVE-2023-28732 and CVE-2023-28733 (AnyMailing/AcyMailing Joomla plugin below 8.3.0 - unauthenticated RCE via unrestricted upload, missing access control and path traversal on the front-office campaign builder). All three sit inside the 6.0.0 to below-10.11.1 range and need no separate row.

Is my site affected?

Affected
AcyMailing from 6.0.0 up to but not including 10.11.1
Fixed in
10.11.1
What to do
Update AcyMailing to 10.11.1 for this flaw, or to 11.1.0 or later, which no rule we check matches.

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

9.2 Critical

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

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:P Attack requirements
Present. Needs a particular deployment or race to line up
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:L Integrity
Low. Some data can be altered
VA:L Availability
Low. The site slows or stutters

What it does beyond the site

SC:H Confidentiality
High. Data on other systems can be read
SI:H Integrity
High. Other systems can be altered
SA:H Availability
High. Other systems can be taken down

Timeline

  1. 9 July 2026CVE-2026-56292 record published by its CNA
  2. 9 July 2026mySites.guru check added for AcyMailing (from 6.0.0 up to but not including 10.11.1)
  3. 9 July 2026We published: Unauthenticated SQL Injection in AcyMailing found by mySites.guru

Rule details

Our disclosure post

Other vulnerabilities in AcyMailing

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

AcyMailing

Latest safe version: 11.1.0

References

CVE-2026-56292 questions

Which versions are affected by CVE-2026-56292?
CVE-2026-56292 affects AcyMailing from 6.0.0 up to but not including 10.11.1. The fix is in 10.11.1.
How do I fix CVE-2026-56292?
Update AcyMailing to 10.11.1 for this flaw, or to 11.1.0 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-56292?
Joomla CNA scores it 9.2 (Critical) 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.