Qwik City CSRF protection middleware does not work properly for content type header with parameters (eg. multipart/form-data)
Summary
A typo in the regular expression within isContentType causes incorrect parsing of certain Content-Type headers.
Impact
An attacker can bypass Qwik City’s Origin-based CSRF protections and perform forged form submissions, potentially causing unauthorized state changes.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | @builder.io/qwik-city | < 1.12.0 | 1.12.0 |
References
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:N- Weakness (CWE)
CWE-352- Platform
- npm
- Package
@builder.io/qwik-city- Disclosed
- 03.02.2026
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-vm6g-8r4h-22x8 - CC BY 4.0
Vulnerability history: @builder.io/qwik-city
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 8
- First → latest
- 04.2023 03.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 2
- High 1
- Medium 4
- Low 1
Disclosures per year
- 2023: 1
- 2024: 0
- 2025: 1
- 2026: 6
-
Qwik City CSRF protection middleware does not work properly for content type header with parameters (eg. multipart/form-data) this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.