CVE-2026-8054 Scanner
CVE-2026-8054 Scanner - SQL Injection (SQLi) vulnerability in dotCMS Core
Short Info
Level
Single Scan
Single Scan
Can be used by
Asset Owner
Estimated Time
10 seconds
Time Interval
18 days 18 hours
Scan only one
Domain, Subdomain, IPv4
Toolbox
The dotCMS Core is an open-source content management system used by various enterprises to manage digital content effectively. Developed by dotCMS, it serves to streamline content creation and delivery with its robust platform. The software is versatile, designed to be used across multiple digital channels, enhancing the customer experience. Its purpose includes facilitating easy integration for developers and providing marketers with intuitive tools. This CMS is valued for its ability to support a wide array of digital marketing strategies, providing the flexibility and functionality needed for content-rich websites.
SQL Injection (SQLi) is a type of injection attack that makes it possible to execute malicious SQL statements. DotCMS Core is vulnerable to SQL Injection due to unsanitized input in its Publish Audit API endpoints. This vulnerability could allow a remote unauthenticated attacker to interact with the back-end database arbitrarily. SQL Injection can result in unauthorized viewing of user data, or it may target the system for modification of data or execution of administrative operations on the database. Preventing SQL Injection vulnerabilities involves using parameterized queries to ensure correct and safe query execution.
The SQL Injection vulnerability in dotCMS Core is found within the Publish Audit API, specifically at the endpoints /api/auditPublishing/get and /api/auditPublishing/getAll. The vulnerability arises from a lack of input sanitization, which allows attackers to inject arbitrary SQL commands. This injection occurs by manipulating input strings to alter database query execution. Exploitation requires crafting specific payloads that induce the database to perform unauthorized operations. By exploiting this, attackers can trigger unauthorized sleeps or injections that disrupt normal database behavior.
If exploited, this vulnerability can have significant consequences, such as enabling attackers to read, modify, or even delete database contents. The entire database may be compromised, leading to unauthorized access to sensitive data. Additionally, attackers could corrupt database integrity, affecting application reliability. In a severe case, this could result in extensive data loss or application downtime. Organizations may face repercussions such as financial loss, reputational damage, or legal liabilities if customer data is exposed.
REFERENCES