Stored XSS via unencoded sname output
Published Mar 23, 2026 · Updated Mar 23, 2026
Stored XSS in /admin/update_s3.php in Code Projects Exam Form Submission 1.0 allows remote authenticated users to execute scripts. The handler writes the sname parameter into an HTML response without output encoding or filtering, so supplied markup runs in a visitor's browser. High-privileged access and a victim page view are required, and successful exploitation modifies browser-displayed content.
Summary
What happened
Stored XSS in /admin/update_s3.php in Code Projects Exam Form Submission 1.0 allows remote authenticated users to execute scripts. The handler writes the sname parameter into an HTML response without output encoding or filtering, so supplied markup runs in a visitor's browser. High-privileged access and a victim page view are required, and successful exploitation modifies browser-displayed content.
The record
- CVE
- CVE-2026-4578
- Published
- Mar 23, 2026
- Updated
- Mar 23, 2026
- Vendor
- Tutorials Website
- Product
- Exam Form Submission
- Classifications
- CWE-79, CWE-94, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 23, 2026CVE publishedPublication date reported by the CVE source.
- Mar 23, 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=1.0
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
- GitHub issue 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