CVE-2026-44739
Authenticated SQL injection in Pimcore reports endpoint allowing DB exfiltration/manipulation
Is CVE-2026-44739 being exploited?
Not confirmed. CVE-2026-44739 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.39% probability of exploitation in the next 30 days.
How severe is CVE-2026-44739?
CVE-2026-44739 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-44739?
Yes. A fix has been recorded for CVE-2026-44739. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-44739 affect?
CVE-2026-44739 affects Pimcore <11.5.17 (LTS), Pimcore <12.3.6, CustomReportsBundle columnConfigAction endpoint, Back-end databases (MySQL/MariaDB/etc.). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-44739?
Upgrade to 11.5.17 or 12.3.6; revoke reports_config access; block endpoint until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Auth user with reports_config can execute arbitrary SELECT/UNION and DB functions to exfiltrate or alter database data.
Immediate action required
- affected< 11.5.17
- affected>= 12.0.0 and < 12.3.6
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.