Browser script execution via unencoded error response
Published Mar 11, 2026 · Updated Mar 11, 2026
Reflected XSS in Locker 0.0.0, 0.0.1, and 0.1.0 allows remote attackers to execute JavaScript via a crafted auth ID. The authIsAwesome function concatenates req.params.id directly into a res.send error body without sanitization or output encoding. A victim must open the crafted /auth/:id URL; the payload then runs in that victim's browser in the Locker origin.
Summary
What happened
Reflected XSS in Locker 0.0.0, 0.0.1, and 0.1.0 allows remote attackers to execute JavaScript via a crafted auth ID. The authIsAwesome function concatenates req.params.id directly into a res.send error body without sanitization or output encoding. A victim must open the crafted /auth/:id URL; the payload then runs in that victim's browser in the Locker origin.
The record
- CVE
- CVE-2026-3951
- Published
- Mar 11, 2026
- Updated
- Mar 11, 2026
- Vendor
- The Locker Project
- Product
- Locker
- Classifications
- CWE-79, CWE-94, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2026CVE publishedPublication date reported by the CVE source.
- Mar 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.0.0
- Affected versionversion=0.0.1
- Affected versionversion=0.1.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Locker issue 963 reflected-XSS proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo