rootpwn

low · CVSS v3 3.1

CVE-2026-102279

Laravel exception debug pages with APP_DEBUG=true can expose attacker-controlled input to a Tippy.js tooltip that allows HTML, leading to DO

Overview

Laravel exception debug pages with APP_DEBUG=true can expose attacker-controlled input to a Tippy.js tooltip that allows HTML, leading to DOM-based XSS when users hover over the tooltip. The flaw exists in Laravel 12.x before 12.69.0 and 13.x before 13.30.0. It is fixed in the newer releases.

Description

Laravel is a web application framework. Prior to 12.69.0 and 13.30.0, Laravel exception debug pages with APP_DEBUG=true pass attacker-controlled input to a Tippy.js tooltip configured with allowHTML true, enabling DOM-based cross-site scripting when a user hovers over the tooltip. This issue is fixed in versions 12.69.0 and 13.30.0.

Impact

Defenders should be aware that attackers can inject malicious scripts into the UI of any site running a vulnerable Laravel version, compromising confidentiality, integrity, and availability of the web application and potentially the users’ browsers. The attack requires the target to have APP_DEBUG enabled and a user to hover over the tooltip.

Remediation

Upgrade Laravel to 12.69.0 or newer, or 13.30.0 or newer. If upgrading is not immediately possible, disable APP_DEBUG in production, or configure Tippy.js to set allowHTML=false and sanitize any user input before rendering.

Risk context

The CVSS v3 score is 3.1 and the severity is low, indicating a low overall risk. However, because the vulnerability is only exploitable when debug mode is enabled, the practical risk in production environments is minimal.

Affected products

  • Laravel 12.x
  • Laravel 13.x

Scores

Severity
low
CVSS v2
2.6
CVSS v3
3.1
CVSS v4
—
EPSS
—

Laravel XSS DOM Tippy.js debug low

← All CVEs

Related CVEs

low

CVE-2026-101265

A vulnerability was identified in Intelbras TIP 125i 4.3.35/4.3.41. The affected element is an unknown function of the component Básico Page. Such manipulation leads to inclusion of sensitive information in source code. The attack can be launched remotely. A high complexity level is associated with this attack. The exploitability is described as difficult. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure.

View analysis

low

CVE-2026-18416

The CoAP link-format helper match_path_uri() in subsys/net/lib/coap/coap_link_format.c compares a registered resource path against the URI carried in a Uri-Query href= option. That URI is not NUL terminated, but the inner character loop advanced its index k once per path character without ever testing it against the option length len. When a registered path segment is longer than the supplied URI and the URI is a prefix of it, the loop reads uri[len] and beyond, past the end of the option value. The path is reached from coap_well_known_core_get_len() and coap_well_known_core_get() via match_queries_resource(), i.e. by any unauthenticated GET /.well-known/core?href=/ request to a device that serves /.well-known/core (for the CoAP server subsystem, CONFIG_COAP_SERVER_WELL_KNOWN_CORE, default y) and has at least one resource that declares struct coap_core_metadata attributes. The over-read does not reach the receive buffer. The well-known-core builders parse the query into a stack-local struct coap_option, whose value is a fixed array (value[12], or CONFIG_COAP_EXTENDED_OPTIONS_LEN_VALUE bytes) that the option bytes are copied into, so uri points into that copy. Reading past len therefore reads the unused, uninitialized tail of the array and, when the option fills it, the bytes just past it in the same stack frame. (In the ZoAP library of v1.8.0 to v1.9.x the option value was instead a pointer into the received packet, and the over-read ran past the option inside the packet buffer.) The impact is bounded. The number of bytes read past the end is limited by the length of the resource path segment, and each additional byte is only read if it happens to equal the next path character, so in practice the over-read is one byte. It also cannot influence the response: returning a match requires the final compared index to be len - 1 or len, both in bounds, so out-of-bounds bytes only ever steer the loop to the next candidate resource. The consequence is undefined behaviour, not information disclosure and not a matching error. The fix adds a k >= len guard at the top of the inner loop, so every uri[k] dereference is within the option value while still allowing a trailing * wildcard to match a longer path.

View analysis

low

CVE-2026-101079

A vulnerability was found in agentverus agentverus-scanner up to 0.8.1. Affected by this vulnerability is the function isSecurityDefenseSkill of the file dist/scanner/analyzers/context.js. Performing a manipulation results in reliance on untrusted inputs in a security decision. The attack must be initiated from a local position. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.

View analysis

low

CVE-2026-97399

The strncasecmp function in the GNU C Library 2.24 and later optimized for the Power8 architecture may read one byte beyond the input size limit, which may crash a program when that byte is not readable. This condition may happen when the input strings to the strncasecmp function are attacker controlled in an application and they match all the way up to the edge of their page and the neighbouring page is either not mapped or is not readable.

View analysis