CVE-2026-8054 Unauthenticated SQL Injection in dotCMS Publish Audit API
Unauthenticated attackers can exploit SQL injection in dotCMS Publish Audit API to read, modify, or destroy arbitrary database content.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-8054?
CVE-2026-8054 is a critical SQL injection vulnerability in dotCMS Core, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in the Publish Audit API endpoints (/api/auditPublishing/get and /api/auditPublishing/getAll) in dotCMS Core 25.11.04-1 through 26.04.28-02 allows remote unauthenticated attackers to read, modify, or destroy arbitrary database content. The endpoints did not enforce authentication and accepted unsanitized input used in dynamically constructed SQL. The fix in dotCMS Core 26.04.28-03 requires an authenticated backend user with the publishing-queue portlet permission. LTS releases are not affected as the vulnerable code path was never backported.
Weakness: CWE-89
Which versions are affected by CVE-2026-8054?
How do I fix CVE-2026-8054?
No fix has been published for CVE-2026-8054 yet. Limit exposure of the affected software until one is available.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-8054 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8054 exists.
Public exploit code: 1 Nuclei template and 1 proofs of concept on GitHub.
Sources
Also known as GHSA-jpx3-25r2-jq5g.