CVE-2026-77378 in Boltinfo

Summary

by MITRE • 11/20/2026

Bolt is a fully open source, adaptable platform for building and running modern websites. Prior to 6.1.4, SQL injection in ListFormatHelper allows authenticated users with upload permission to execute arbitrary SQL queries through /async/select-options and exfiltrate sensitive database contents when general/caching/list_format is enabled. This issue is fixed in version 6.1.4.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 11/20/2026

Bolt CMS represents a fully open-source, adaptable platform designed for building and running modern websites, offering flexibility to developers and content managers alike. However, prior to the release of version 6.1.4, the system contained a critical security flaw within its ListFormatHelper component that exposed sensitive database information to authenticated attackers. This vulnerability specifically affects environments where the configuration setting general/caching/list_format is enabled, which is common in many deployments to improve performance by caching list formats for content types and fields.

The core technical flaw constitutes an SQL injection vulnerability located within the /async/select-options endpoint. When a user with upload permissions interacts with this endpoint, they can manipulate input parameters that are subsequently passed directly into database queries without adequate sanitization or parameterization. Because Bolt CMS relies on standard PHP data handling practices in certain legacy code paths, the application fails to properly escape special characters used in SQL syntax. This allows an attacker to construct malicious payloads that alter the logic of backend SQL statements. The vulnerability is particularly dangerous because it does not require administrative privileges; any authenticated user with the ability to upload content can exploit this flaw, significantly lowering the barrier for entry compared to high-privilege vulnerabilities.

The operational impact of this vulnerability is severe, primarily centering on unauthorized data exfiltration and potential database manipulation. By exploiting the SQL injection in ListFormatHelper, an attacker can execute arbitrary SQL queries against the underlying database. This capability allows the extraction of sensitive information such as user credentials, session tokens, personal identifiable information stored within content records, and other proprietary data housed in the Bolt CMS database. Furthermore, depending on the specific capabilities granted to the database user account running the web application, an attacker might be able to modify or delete existing data, leading to integrity violations and potential service disruption through destructive queries such as DROP TABLE commands.

From a classification perspective, this vulnerability aligns with CWE-89 Improper Neutralization of Special Elements used in an SQL Command, commonly known as SQL Injection. In the context of the MITRE ATT&CK framework, this exploit maps to T1059 Command and Scripting Interpreter for executing arbitrary commands via injected code, and specifically relates to data exfiltration techniques where structured query language is abused to retrieve unauthorized information from a database backend. The attack vector involves authenticated users leveraging their existing session tokens to interact with the application interface, making detection through standard network monitoring tools difficult without specific behavioral analysis of SQL patterns in web traffic logs.

To mitigate this risk and secure Bolt CMS installations, immediate action must be taken by upgrading to version 6.1.4 or any later release where the ListFormatHelper has been patched to properly sanitize inputs and use parameterized queries. For organizations unable to upgrade immediately due to dependency constraints, temporary mitigations include restricting access to the /async/select-options endpoint through web application firewall rules that detect common SQL injection patterns in query parameters. Additionally, ensuring that the database user account operates with minimal privileges can limit the damage an attacker could cause even if exploitation occurs. Regular security audits and code reviews focusing on data handling practices are recommended to prevent similar vulnerabilities from being introduced during future development cycles.

Responsible

GitHub M

Reservation

08/20/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00290

KEV

no

Activities

very low

Sources

Do you want to use VulDB in your project?

Use the official API to access entries easily!