VulnerabilityPublished 3 Feb 2026

CVE-2026-25148: QwikDev qwik · Cross-site Scripting

Affects QwikDev qwikSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.19.0 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.19.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: Low
Subsequent system integrity: Low
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Subsequent System.
Subsequent system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Subsequent System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade qwik and qwikdev/qwik to 1.19.0.

Affected software

Product	Affected	Fixed in
QwikDevqwik	Affected <1.19.0	Fixed in 1.19.0
npmqwikdev/qwik`pkg:npm/qwikdev/qwik`Other threats	Affected <1.19.0	Fixed in 1.19.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade all Qwik framework instances to version 1.19.0 or later immediately to apply the official patch addressing this vulnerability.
Conduct a thorough audit of server-side rendering code to identify any custom serialization or handling of virtual attributes that may bypass framework protections.
Implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and mitigate the impact of potential XSS attacks.
Employ input validation and output encoding best practices in all web application components, especially those interacting with user-supplied data.
Monitor web application logs and user reports for suspicious activity indicative of XSS exploitation attempts.
Educate developers on secure coding practices related to server-side rendering and JavaScript frameworks to prevent similar vulnerabilities.
Consider using automated security scanning tools that can detect XSS vulnerabilities in web applications during development and deployment cycles.
If immediate upgrade is not feasible, apply temporary mitigations such as disabling server-side rendering of virtual attributes or sanitizing inputs at the application layer.

Description

CVE-2026-25148 is a medium severity Cross-Site Scripting (XSS) vulnerability in Qwik, a JavaScript framework focused on performance. Versions prior to 1.19.0 are affected due to improper neutralization of input during server-side rendering of virtual attributes, allowing remote attackers to inject malicious scripts. Exploitation requires no authentication but does require user interaction to trigger script execution in the victim's browser within the affected origin context. This vulnerability can lead to theft of sensitive information, session hijacking, or other malicious actions performed on behalf of the user. The issue has been patched in Qwik version 1.19.0. European organizations using affected Qwik versions in web applications are at risk, especially those with public-facing services.

Impact

For European organizations, this vulnerability can lead to significant security risks including theft of session cookies, user credentials, or other sensitive information through script injection. Attackers could perform actions on behalf of users, leading to account compromise or data leakage. Public-facing web applications built with vulnerable Qwik versions are particularly at risk, potentially affecting customer trust and regulatory compliance under GDPR due to data breaches. The medium severity score indicates moderate impact, but the widespread use of JavaScript frameworks in Europe’s digital economy means a broad attack surface. Organizations in sectors such as finance, e-commerce, and government services are especially vulnerable due to the sensitive nature of their data and high-value targets for attackers. Additionally, the vulnerability could be leveraged as part of multi-stage attacks or social engineering campaigns. Although no known exploits exist currently, the ease of exploitation and lack of required privileges make timely patching critical to prevent potential compromise.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Feb 2026, 11:58 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats