Reflected XSS via unescaped request URL output
Published Nov 20, 2024 · Updated Apr 8, 2026
Reflected XSS in Aaron J 404 Solution 2.35.19 and earlier allows remote attackers to run scripts through crafted 404 request URLs. Published sources identify the vulnerable locus only as URL handling and do not disclose the function; that path emits attacker-controlled URL data without sufficient sanitization or output escaping. Execution requires a user to follow a crafted link; the injected script then runs in that user's browser context, allowing page data to be read or altered.
Summary
What happened
Reflected XSS in Aaron J 404 Solution 2.35.19 and earlier allows remote attackers to run scripts through crafted 404 request URLs. Published sources identify the vulnerable locus only as URL handling and do not disclose the function; that path emits attacker-controlled URL data without sufficient sanitization or output escaping. Execution requires a user to follow a crafted link; the injected script then runs in that user's browser context, allowing page data to be read or altered.
The record
- CVE
- CVE-2024-11277
- Published
- Nov 20, 2024
- Updated
- Apr 8, 2026
- Vendor
- AJ Experience
- Product
- 404 Solution
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 20, 2024CVE publishedPublication date reported by the CVE source.
- Apr 8, 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 <=2.35.19
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