<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Dotcms on Aretiq AI</title><link>https://aretiq.ai/tags/dotcms/</link><description>Recent content in Dotcms on Aretiq AI</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 27 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aretiq.ai/tags/dotcms/index.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-8054 — dotCMS Core Publish Audit API SQL Injection</title><link>https://aretiq.ai/research/vul260527-cve-2026-8054-dotcms-core-publish-audit-api-sql-injection/</link><pubDate>Wed, 27 May 2026 00:00:00 +0000</pubDate><guid>https://aretiq.ai/research/vul260527-cve-2026-8054-dotcms-core-publish-audit-api-sql-injection/</guid><description>&lt;h2 id="1-overview">1. Overview&lt;/h2>
&lt;p>A critical SQL injection vulnerability exists in the dotCMS Core content management system&amp;rsquo;s Publish Audit API. The &lt;code>/api/auditPublishing/getAll&lt;/code> REST endpoint accepts a JSON array of bundle identifiers and passes them unsanitized into a SQL query via string concatenation, allowing an attacker to inject arbitrary SQL statements. The endpoint requires no authentication, enabling an unauthenticated remote attacker to read, modify, or destroy the entire dotCMS PostgreSQL database with a single HTTP request. dotCMS addressed this vulnerability in version 26.04.28-03 by parameterizing the SQL query and adding Push Publish JWT token authentication to the affected endpoints.&lt;/p></description></item></channel></rss>