Contributor-level stored XSS via insufficient output escaping
Published Nov 19, 2024 · Updated May 11, 2026
Stored XSS in Kyle M Brown Step by Step 0.4.5 and earlier allows remote authenticated users to inject scripts into pages. The public advisories attribute the flaw to insufficient input sanitization and output escaping but do not identify the affected field or function. Contributor-level access is required, and the payload executes when another user views the injected page.
Summary
What happened
Stored XSS in Kyle M Brown Step by Step 0.4.5 and earlier allows remote authenticated users to inject scripts into pages. The public advisories attribute the flaw to insufficient input sanitization and output escaping but do not identify the affected field or function. Contributor-level access is required, and the payload executes when another user views the injected page.
The record
- CVE
- CVE-2024-50535
- Published
- Nov 19, 2024
- Updated
- May 11, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, CAPEC-592, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 19, 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?
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
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