# 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.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-jpx3-25r2-jq5g

## 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 (Improper Neutralization of Special Elements used in an SQL Command)

## 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.

## 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:

- dotCMS Pre-auth SQL Injection (github_poc): https://github.com/Mr-xn/CVE-2026-8054
- dotCMS Core Publish Audit API - Unauthenticated SQL Injection (nuclei): http/cves/2026/CVE-2026-8054.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8054 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8054 exists.

Affected product: dotCMS Core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8054/ (Markdown: https://insights.sbomify.com/CVE-2026-8054/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8054
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8054
- OSV: https://osv.dev/vulnerability/CVE-2026-8054

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8054/
Summaries are generated and may contain mistakes; the official description above is the record.