Cross-user script execution via stored module code
Published Mar 1, 2023 · Updated Mar 7, 2025
Stored XSS in vxcontrol SOLDR 1.1.0 allows remote authenticated users to run scripts in another user's browser via the module editor. The editor stores attacker-controlled JavaScript in a module's main.vue file and renders that file as executable content when the module is opened. A low-privileged account must create or edit a module, and a higher-privileged user must open it; the script then acts with the victim's application privileges and can access the WebSocket service through the valid origin.
Summary
What happened
Stored XSS in vxcontrol SOLDR 1.1.0 allows remote authenticated users to run scripts in another user's browser via the module editor. The editor stores attacker-controlled JavaScript in a module's main.vue file and renders that file as executable content when the module is opened. A low-privileged account must create or edit a module, and a higher-privileged user must open it; the script then acts with the victim's application privileges and can access the WebSocket service through the valid origin.
The record
- CVE
- CVE-2023-26608
- Published
- Mar 1, 2023
- Updated
- Mar 7, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 1, 2023CVE publishedPublication date reported by the CVE source.
- Mar 7, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Upstream stored-XSS reproduction stepsproof 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