PoC Monitor
← All CVEs
CVE-2026-8054published 27 May 2026 07:55 UTCData: JSON · API

dotCMS Core

Unauthenticated SQL Injection in dotCMS Publish Audit API

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.

First public PoC 13 daysafter publication · 9 Jun 2026
Public PoCs21 on GitHub · 1 Exploit-DB, Metasploit or nuclei
CVSS10.0critical · scored by CNA · CWE-89
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

dotCMS dotCMS Core
  • >= 25.11.04-1, <= 26.04.28-02

Fixed in 26.04.28-03

Mitigation

Upgrade dotCMS Core to 26.04.28-03 or later.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8+10+12+14CVE published27 May 2026 · t = 0First public PoC9 Jun 2026 · t+13d

First public PoC 13 days after publication; not in CISA KEV. First PoC: Mr-xn/CVE-2026-8054 (created 9 Jun 2026, found by us: backfilled).

PoC repositories

Found on GitHub.

1 PoCs

PoCs 1
RepositoryCreatedStarsAssessment
Mr-xn/CVE-2026-8054 9 Jun 2026 +13 d 0 PoC

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.

Other public exploits

Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.
SourceTitlePublishedFound by us
nuclei templatenuclei template: dotCMS Core Publish Audit API - Unauthenticated SQL Injection9 Jun 202614 Nov 2026

PoC characteristics

What to hunt for in your logs · from 1 PoC repo

Regex

Generated from PoC characteristics; not yet reviewed. Matches the request path and query.

POST /api/auditPublishing/getAll
(?i)^/api/auditPublishing/getAll(?:[?#].*)?$

Suricata

Template generated from PoC characteristics. Review before deploying.

POST /api/auditPublishing/getAll
alert http any any -> $HOME_NET [8080] (msg:"GG PoC-Monitor CVE-2026-8054 dotCMS dotCMS Core exploit attempt"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/api/auditPublishing/getAll"; reference:url,poc.griffinguard.io/cve/CVE-2026-8054; classtype:web-application-attack; sid:9638492; rev:1;)

Sigma

Template generated from PoC characteristics. Review before deploying.

POST /api/auditPublishing/getAll
title: dotCMS dotCMS Core exploit attempt (CVE-2026-8054)
id: gg-pocmon-cve-2026-8054-9638492
status: experimental
description: Request pattern taken from public PoCs for CVE-2026-8054. Generated, not reviewed.
references:
  - https://poc.griffinguard.io/cve/CVE-2026-8054
logsource:
  category: webserver
detection:
  selection:
    cs-method: POST
    cs-uri-stem|contains|all:
      - '/api/auditPublishing/getAll'
  condition: selection
falsepositives:
  - Authorized vulnerability scanning
level: critical
tags:
  - attack.initial_access
  - attack.t1190
  - cve.2026.8054