Stored XSS via forged privileged-user requests
Published Oct 17, 2024 · Updated May 11, 2026
CSRF in GabbyKhrmon Wsify Widget 1.0 and earlier allows remote attackers to store script code through a forged request. Patchstack identifies the result as stored XSS but does not disclose the affected endpoint, parameter, or missing request validation. Exploitation requires a privileged user with an active session to open attacker-controlled content, after which the stored script executes for later visitors.
Summary
What happened
CSRF in GabbyKhrmon Wsify Widget 1.0 and earlier allows remote attackers to store script code through a forged request. Patchstack identifies the result as stored XSS but does not disclose the affected endpoint, parameter, or missing request validation. Exploitation requires a privileged user with an active session to open attacker-controlled content, after which the stored script executes for later visitors.
The record
- CVE
- CVE-2024-48048
- Published
- Oct 17, 2024
- Updated
- May 11, 2026
- Vendor
- GabbyKhrmon
- Product
- Wsify Widget
- Classifications
- CWE-352, CAPEC-592, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 17, 2024CVE publishedPublication date reported by the CVE source.
- May 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 <=1.0
What conditions does exploitation require?
What is affected?
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
No public exploit references are available in this record.
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