slim/slim

CVE-2026-48157

CVE-2026-48157 is a medium-severity cross-site scripting (XSS) vulnerability in slim/slim (composer), affecting versions >= 4.4.0, <= 4.15.1. It is fixed in 4.15.2.

Key facts
CVSS score
6.1
Medium
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
slim/slim
Fixed in
4.15.2
Disclosed
2026

Summary

Impact 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. Patches The issue is fixed in 4.15.2. Workarounds Without upgrading, applications can: Avoid passing untrusted/request-derived data into HttpException::setTitle() and setDescription(). Use static, plain-text error copy instead. Register a custom error renderer (an ErrorRendererInterface implementation, or a subclass of HtmlErrorRenderer that escapes the title and description) for the HTML media type. Acknowledgments Slim is grateful to and thanks GitHub user 0xEr3n for reporting this issue. Resources CWE-79: https://cwe.mitre.org/data/definitions/79.html

Impact

What is cross-site scripting (XSS)?

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

Severity and exposure

CVE-2026-48157 has a CVSS score of 6.1 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (4.15.2). Upgrading removes the vulnerable code path.

Affected versions

composer

  • slim/slim (>= 4.4.0, <= 4.15.1)

Security releases

  • slim/slim → 4.15.2 (composer)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-48157 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-48157 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2026-48157 in your environment

Remediation advice

Upgrade slim/slim to 4.15.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-48157

What is CVE-2026-48157?

CVE-2026-48157 is a medium-severity cross-site scripting (XSS) vulnerability in slim/slim (composer), affecting versions >= 4.4.0, <= 4.15.1. It is fixed in 4.15.2. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2026-48157?

CVE-2026-48157 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of slim/slim are affected by CVE-2026-48157?

slim/slim (composer) versions >= 4.4.0, <= 4.15.1 is affected.

Is there a fix for CVE-2026-48157?

Yes. CVE-2026-48157 is fixed in 4.15.2. Upgrade to this version or later.

Is CVE-2026-48157 exploitable, and should I be worried?

Whether CVE-2026-48157 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-48157 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-48157?

Upgrade slim/slim to 4.15.2 or later.

Stop the waste.
Protect your environment with Kodem.