Stored script execution via unsanitized web fields
Published Oct 22, 2024 · Updated Oct 22, 2024
Stored XSS in YSoft SafeQ 6 Build 53 allows remote authenticated users to execute JavaScript in other users' browsers. Multiple editable web fields persist attacker-controlled input and render it without output sanitization when legitimate users open affected pages. Valid credentials are required to plant a payload, and another user must view the stored content, exposing that browser session to attacker-scripted actions.
Summary
What happened
Stored XSS in YSoft SafeQ 6 Build 53 allows remote authenticated users to execute JavaScript in other users' browsers. Multiple editable web fields persist attacker-controlled input and render it without output sanitization when legitimate users open affected pages. Valid credentials are required to plant a payload, and another user must view the stored content, exposing that browser session to attacker-scripted actions.
The record
- CVE
- CVE-2022-23861
- Published
- Oct 22, 2024
- Updated
- Oct 22, 2024
- Vendor
- Y Soft
- Product
- YSoft SafeQ 6
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 22, 2024CVE publishedPublication date reported by the CVE source.
- Oct 22, 2024Record 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=6_build_53
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
- SafeQ stored-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