Browser script execution via reflected username
Published Jan 13, 2024 · Updated Jun 16, 2025
Reflected XSS in QStar Archive Solutions RELEASE_3-0 Build 7 Patch 0 allows remote attackers to run JavaScript via a crafted link. The login task accepts a script payload in the username parameter and reflects it into the victim's browser without neutralization. Exploitation requires the victim to click the crafted link, after which the demonstrated payload executes in that user's browser context.
Summary
What happened
Reflected XSS in QStar Archive Solutions RELEASE_3-0 Build 7 Patch 0 allows remote attackers to run JavaScript via a crafted link. The login task accepts a script payload in the username parameter and reflects it into the victim's browser without neutralization. Exploitation requires the victim to click the crafted link, after which the demonstrated payload executes in that user's browser context.
The record
- CVE
- CVE-2023-51067
- Published
- Jan 13, 2024
- Updated
- Jun 16, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 13, 2024CVE publishedPublication date reported by the CVE source.
- Jun 16, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- QStar login username 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