Browser script execution via unencoded user name
Published May 8, 2026 · Updated May 8, 2026
Stored XSS in SourceCodester Pharmacy Sales and Inventory System 1.0 allows remote authenticated users to run scripts in another user's browser. The users page outputs the attacker-controlled name value directly into HTML without encoding or filtering, causing injected script elements to execute as content. Exploitation requires high privileges and passive interaction by a viewer under the CNA assessment; the public report instead claims that no login is required.
Summary
What happened
Stored XSS in SourceCodester Pharmacy Sales and Inventory System 1.0 allows remote authenticated users to run scripts in another user's browser. The users page outputs the attacker-controlled name value directly into HTML without encoding or filtering, causing injected script elements to execute as content. Exploitation requires high privileges and passive interaction by a viewer under the CNA assessment; the public report instead claims that no login is required.
The record
- CVE
- CVE-2026-8136
- Published
- May 8, 2026
- Updated
- May 8, 2026
- Vendor
- Online Computer and Laptop Store Project
- Product
- Pharmacy Sales and Inventory System
- Classifications
- CWE-94, CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 8, 2026CVE publishedPublication date reported by the CVE source.
- May 8, 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=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
- Name-parameter script-injection 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