Security readout for executives and security teams
Plain-English summary
Pimcore versions before 12.3.1 and 11.5.14 may let a logged-in backend user view static route configurations they should not access. This is an information disclosure issue, not a system takeover. Business urgency is moderate where many backend users exist or route data reveals sensitive application structure.
Executive priority
Prioritize remediation during the next routine security update cycle, sooner for shared or heavily delegated Pimcore administration. The issue is authenticated and confidentiality-only, but leaked routing details can aid attackers already inside the backend.
Technical view
CVE-2026-23494 is a missing function-level authorization flaw in Pimcore’s static routes listing API. An authenticated backend user without explicit permissions could retrieve route configuration details, including patterns, controllers, variables, and priorities. Affected ranges are Pimcore >=12.0.0-RC1 and <12.3.1, and versions <11.5.14. CVSS is 4.3, AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N.
Likely exposure
Exposure is limited to Pimcore deployments with backend users who can authenticate but should not view static route configuration. Risk is higher in multi-user administrative environments, agencies, or shared operations teams where backend accounts have varied trust levels.
Exploitation context
Sources do not report active exploitation, and the CVE is not marked KEV. Exploitation requires authenticated backend access. The primary impact is confidentiality loss: route definitions may reveal application internals useful for reconnaissance or subsequent abuse.
Researcher notes
The public record identifies CWE-284 and a server-side authorization gap. The fix is referenced through Pimcore releases and pull request 18893. Public sources do not provide evidence of unauthenticated access, integrity impact, availability impact, or exploitation in the wild.
Mitigation direction
- Upgrade Pimcore 12.x deployments to 12.3.1 or later.
- Upgrade Pimcore 11.x deployments to 11.5.14 or later.
- Review backend user roles and remove unnecessary access.
- Monitor Pimcore advisory and release pages for updated guidance.
Validation and detection
- Inventory all Pimcore instances and record exact versions.
- Compare versions against affected ranges in the advisory.
- Confirm fixed versions 12.3.1 or 11.5.14 are deployed.
- Verify low-privilege backend users cannot view static route listings.
- Review logs for unusual backend access to static route functionality.
Public sources used
Automatically approved under Michael Williams's editorial policy. This source version was not individually reviewed.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-23494 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/pimcore/pimcore/security/advisories/GHSA-m3r2-724c-pwgfCVE reference · x_refsource_CONFIRM
- https://github.com/pimcore/pimcore/pull/18893CVE reference · x_refsource_MISC
- https://github.com/pimcore/pimcore/releases/tag/v11.5.14CVE reference · x_refsource_MISC
- https://github.com/pimcore/pimcore/releases/tag/v12.3.1CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.