Pimcore (>= 2026.1.0, <= 2026.1.5) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/pimcore--2026.1.0--2026.1.5/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioFri, 11 Sep 2026 00:55:23 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgSQL Injection in Pimcore CustomReportsBundlehttps://feed.craftedsignal.io/briefs/2026-09-pimcore-sql-injection/Fri, 11 Sep 2026 00:55:23 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-09-pimcore-sql-injection/An authenticated SQL injection vulnerability in Pimcore's CustomReportsBundle allows users with specific permissions to execute arbitrary database commands by bypassing a weak keyword blacklist.Pimcore is susceptible to a high-severity SQL injection vulnerability identified as CVE-2026-55416, affecting the CustomReportsBundle. The issue originates in the Sql.php adapter, where user-supplied configuration fields - specifically sql, from, where, and groupby - are concatenated directly into database queries. While the application implements a regex-based blacklist to filter malicious keywords, the current implementation is insufficient. It fails to block critical SQL injection primitives such as UNION SELECT, INSERT, subqueries, and MySQL comment injection.

An attacker with reports_config privileges can manipulate these report configuration parameters to gain unauthorized access to the database, including the potential to read, modify, or delete sensitive data. Furthermore, the application fails to cast $offset and $limit parameters to integers, introducing a secondary injection vector via the LIMIT clause. This vulnerability affects multiple branches of Pimcore, including versions within the 2026.x, 12.x, and 11.x release lines.

Attack Chain

  1. Attacker obtains an authenticated session with reports_config permissions.
  2. Attacker initiates an HTTP POST request to /admin/bundle/customreports/custom-report/update.
  3. Attacker embeds malicious SQL payloads within the configuration JSON object fields (e.g., sql, where).
  4. The CustomReportController::updateAction decodes the input and persists the malicious configuration to the custom_reports database table.
  5. The application triggers a data retrieval process, calling Tool\Config::getByName() to load the configuration.
  6. The Sql::buildQueryString method concatenates the malicious input strings to form a query, bypassing the incomplete regex filter.
  7. The final query is executed via $db->fetchAllAssociative($sql), executing the attacker's arbitrary SQL commands.
  8. Attacker retrieves sensitive data or modifies records through the malicious report interface.

Impact

Successful exploitation results in full database compromise. Attackers can exfiltrate sensitive user data, bypass authentication controls, or alter application state. The vulnerability is accessible to any user granted the reports_config permission, which is typically assigned to administrative or reporting roles.

Recommendation

  1. Patch Pimcore immediately by upgrading to versions 2026.1.6, 12.3.10, or 11.5.19 or later.
  2. Review and restrict the reports_config permission to the smallest necessary set of trusted administrative users.
  3. Deploy WAF rules to inspect POST requests to /admin/bundle/customreports/custom-report/update for SQL injection patterns, specifically targeting common clauses like UNION, SELECT, and INFORMATION_SCHEMA in the configuration parameter.
  4. Detection engineers should audit web server logs for suspicious database query patterns originating from the custom reports module.
]]>highadvisorysql-injectionweb-applicationcms