{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 12.3"
      },
      "package": {
        "ecosystem": "Packagist",
        "name": "pimcore/pimcore"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "12.0.0-RC1"
            },
            {
              "fixed": "12.3.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 11.5.13"
      },
      "package": {
        "ecosystem": "Packagist",
        "name": "pimcore/pimcore"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "11.5.14"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-23494"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-284"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-01-15T18:12:49Z",
    "nvd_published_at": "2026-01-15T17:16:08Z",
    "severity": "MODERATE"
  },
  "details": "### Summary\nThe application fails to enforce proper server-side authorization checks on the API endpoint responsible for reading or listing static routes. In Pimcore, static routes are custom URL patterns defined via the backend interface or the var/config/staticroutes.php file, including details like regex-based patterns, controllers, variables, and priorities. These routes are registered automatically through the PimcoreStaticRoutesBundle and integrated into the MVC routing system. Testing revealed that an authenticated backend user lacking explicit permissions was able to invoke the endpoint (e.g., GET /api/static-routes) and retrieve sensitive route configurations. This violates OWASP A01:2021 Broken Access Control, as function-level authorization is absent, allowing unauthorized access to internal routing metadata. Without validation, the endpoint exposes route structures, potentially revealing application architecture, endpoints, or custom logic intended for administrative roles only.\n\n### Details\nThe backend user without permission was still able to list \"Static Routes\" item\n\n### Step to Reproduce the issue\nlogin as Admin (full permission) and clicked \"Static Routes\"\n\u003cimg width=\"945\" height=\"858\" alt=\"Screenshot 2025-12-10 at 9 36 04\u202fPM\" src=\"https://github.com/user-attachments/assets/3d4ce400-9bc2-493e-a899-60d5f42ad307\" /\u003e\nThen, captured and saved the request:\n-List API\n\u003cimg width=\"1122\" height=\"570\" alt=\"Screenshot 2025-12-10 at 9 44 17\u202fPM\" src=\"https://github.com/user-attachments/assets/81dfb589-fe5d-46ed-b5ee-869a49c08557\" /\u003e\n\nNext, login a backend user with no permission\n\u003cimg width=\"1219\" height=\"744\" alt=\"Screenshot 2025-12-10 at 9 06 12\u202fPM\" src=\"https://github.com/user-attachments/assets/1dada4c4-d907-4477-9773-70dea3ef5816\" /\u003e\n\nThe copy the \"Cookie\" and \"X-Pimcore-Csrf-Token\"\n\u003cimg width=\"1902\" height=\"971\" alt=\"Screenshot 2025-12-10 at 9 10 47\u202fPM\" src=\"https://github.com/user-attachments/assets/63221682-fa14-429b-8665-fc9dd8bed890\" /\u003e\n\nAfter that, pasted the copied \"Cookie\" and \"X-Pimcore-Csrf-Token\" to captured request\n\n-List API\n \n\u003cimg width=\"1132\" height=\"829\" alt=\"Screenshot 2025-12-10 at 9 47 27\u202fPM\" src=\"https://github.com/user-attachments/assets/4edea3d1-f5d9-4758-9a07-e9d484c92864\" /\u003e\n\n\n\n### Impact\nExploitation enables low-privileged users to enumerate static routes, gaining reconnaissance into URL patterns, associated controllers, and parameter handling, which could facilitate targeted attacks like path traversal, injection via exposed variables, or discovery of hidden administrative paths. In a Pimcore environment, this might expose site-specific routing for multi-tenant setups, leading to unauthorized data access, workflow manipulation, or escalation to broader system compromise. Business impacts include intellectual property leakage of custom routing logic, regulatory non-compliance (e.g., GDPR for exposed configs), and increased attack surface for chaining with other vulnerabilities.",
  "id": "GHSA-m3r2-724c-pwgf",
  "modified": "2026-01-15T20:17:47Z",
  "published": "2026-01-15T18:12:49Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/pimcore/pimcore/security/advisories/GHSA-m3r2-724c-pwgf"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-23494"
    },
    {
      "type": "WEB",
      "url": "https://github.com/pimcore/pimcore/pull/18893"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/pimcore/pimcore"
    },
    {
      "type": "WEB",
      "url": "https://github.com/pimcore/pimcore/releases/tag/v11.5.14"
    },
    {
      "type": "WEB",
      "url": "https://github.com/pimcore/pimcore/releases/tag/v12.3.1"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Pimcore is Vulnerable to Broken Access Control: Missing Function Level Authorization on \"Static Routes\" Listing"
}