dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-8054

CRITICAL · 10.0 CVSS v4.0 Published 2026-05-27
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in dotCMS Core's Publish Audit API endpoints (/api/auditPublishing/get and /api/auditPublishing/getAll) allows remote unauthenticated attackers to execute arbitrary SQL commands. The endpoints accept unsanitized user input directly into dynamically constructed SQL queries without any authentication enforcement, enabling complete database compromise including read, write, and delete operations.

MitigationUpgrade to dotCMS Core 26.04.28-03 or later which implements authentication requirements for these endpoints. For versions 26.04.28-02 and earlier, implement immediate network-level restrictions to block external access to the vulnerable API endpoints until upgrade is completed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm dotCMS Core is installed
    Look for the dotCMS installation directory or check running services. Common paths: /dotcms/, /opt/dotcms/, or check for java processes running dotcms. Also check if port 8082 (default dotCMS) is listening.
    Affected if dotCMS Core software is found running on the system
  2. Identify the installed dotCMS version
    Check the version file in the dotCMS installation, typically found in the bin/version.properties or bin/dotcms-config.properties file. Alternatively, access the /api/about endpoint if available.
    Affected if The installed version is 26.04.28-02 or earlier, or if the version cannot be determined and the product is confirmed as dotCMS Core
  3. Verify unauthenticated access to auditPublishing endpoints
    Send an HTTP GET request to both /api/auditPublishing/get and /api/auditPublishing/getAll endpoints without providing any authentication credentials (no cookies, tokens, or Basic Auth). Use curl: curl -v http://TARGET_HOST:PORT/api/auditPublishing/get
    Affected if The endpoints return a valid HTTP response (200 OK) without requiring authentication, indicating the vulnerability is exploitable
  4. Test for SQL injection in the endpoint parameters
    Send a crafted request with SQL injection payloads to /api/auditPublishing/get, for example: curl 'http://TARGET:PORT/api/auditPublishing/get?id=1%27%20OR%201=1--' to see if unsanitized input is reflected in database errors or altered behavior.
    Affected if The application returns database error messages, behaves differently with injection payloads, or the request is processed without error when it should fail, confirming SQL injection is possible
  5. Check network accessibility of vulnerable endpoints
    Determine if the dotCMS API ports (typically 8082 or configured HTTP port) are exposed to untrusted networks. Use netstat or nmap: nmap -p 8082 TARGET to check if the port is accessible from outside the local network.
    Affected if The dotCMS HTTP port is accessible from external/untrusted networks, allowing unauthenticated attackers to reach the vulnerable endpoints

A system is affected if it runs dotCMS Core version 26.04.28-02 or earlier AND the /api/auditPublishing/* endpoints are accessible without authentication from a network perspective.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to dotCMS Core 26.04.28-03 or later which implements authentication requirements for these endpoints. For versions 26.04.28-02 and earlier, implement immediate network-level restrictions to block external access to the vulnerable API endpoints until upgrade is completed.

Recommended fix High confidence

dotCMS Core 26.04.28-03

  1. Upgrade dotCMS Core from any version 25.11.04-1 through 26.04.28-02 to version 26.04.28-03
  2. After upgrading, ensure that any integrations or scripts that consume the /api/auditPublishing/get and /api/auditPublishing/getAll endpoints are updated to include proper authentication
  3. Verify that the authenticated user account used for these API calls has the 'publishing-queue' portlet permission enabled in the dotCMS admin console
  4. Test the upgraded endpoints with valid credentials to confirm they function correctly
Caveat Applications calling these endpoints without authentication will now fail - they must be updated to include authenticated backend user credentials

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8054 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8054 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data