{
  "affected": [
    {
      "ranges": [
        {
          "database_specific": {
            "extracted_events": [
              {
                "introduced": "4.4.0"
              },
              {
                "fixed": "4.15.2"
              }
            ],
            "source": "AFFECTED_FIELD"
          },
          "events": [
            {
              "introduced": "207acac048652a35d4762a737d59e317aedc02df"
            },
            {
              "fixed": "e12cb05ca2a14e8f459d019e87a31dc915b80470"
            }
          ],
          "repo": "https://github.com/slimphp/slim",
          "type": "GIT"
        }
      ]
    }
  ],
  "aliases": [
    "GHSA-53h4-8rc4-f539"
  ],
  "database_specific": {
    "cna_assigner": "GitHub_M",
    "cwe_ids": [
      "CWE-79"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/48xxx/CVE-2026-48157.json"
  },
  "details": "Slim is a PHP micro framework that enables users to write simple web applications and APIs. In versions 4.4.0 through 4.15, if an application uses HttpException::setTitle() and/or setDescription() to include untrusted/request-derived data in the error title or description (e.g. \"No products found matching '{$query}'.\"), an attacker could inject arbitrary HTML/JavaScript that executes in the victim's browser when they encounter an HTML error page generated by Slim. The vulnerability is present even with displayErrorDetails = false as the unescaped title and description are rendered on this error path. Built-in exceptions (HttpNotFoundException, HttpBadRequestException, etc.) ship plain-text defaults, so a vanilla Slim app with no user code is not exploitable. Only applications that feed untrusted data into setTitle() and/or setDescription() are affected. The issue has been fixed in 4.15.2. If developers are unable to immediately update their applications, they can work around this issue by avoiding passing untrusted/request-derived data into HttpException::setTitle() and setDescription() and using static, plain-text error copy instead.\nThey should also register a custom error renderer (an ErrorRendererInterface implementation, or a subclass of HtmlErrorRenderer that escapes the title and description) for the HTML media type.",
  "id": "CVE-2026-48157",
  "modified": "2026-08-04T11:30:56.273333418Z",
  "published": "2026-06-15T20:59:23.876Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/slimphp/Slim/releases/tag/4.15.2"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/48xxx/CVE-2026-48157.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/slimphp/Slim/security/advisories/GHSA-53h4-8rc4-f539"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-48157"
    }
  ],
  "schema_version": "1.8.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Slim has Reflected XSS in the HtmlErrorRenderer"
}