CVE Tools
Track your stack

CVE-2026-8054

Unauthenticated SQL Injection in dotCMS Publish Audit API

No known exploitation. EPSS puts it in the 76th percentile. Fixed in 26.04.28-03.

CVSS —Not scoredEPSS percentile76th1.6% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix26.04.28-03Upgrade to this build

Published Updated Sources: CVE.org, NVD

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • dotCMS CoreAffected: ≥ 25.11.04-1, ≤ 26.04.28-02Upgrade to: after 26.04.28-02Fixed builds26.04.28-03Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Check it yourselfA free Nuclei and OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Discuss checks for your systems with a specialist. Scope is agreed before testing.

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS76th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

1.6% chance of exploitation activity in the next 30 days, which ranks it in the 76th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

6 events over 29 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Nuclei check added
  3. Publishedweakness classified, att&ck mapped, record updated

Affected products

Technical detail

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for dotCMS Core, not every advisory.