Browser script execution via unsanitized user records
Published Jun 5, 2025 · Updated Jun 5, 2025
Stored XSS in saveuser.php in Traffic Offense Reporting System 1.0 allows remote authenticated users to run script in a viewer's browser. The handler inserts user_id, username, email, name, and position POST values into the database without sanitization, and view-users.php renders them without output encoding. A valid session is required to submit the add-user form, and the payload executes when another user opens the user list, enabling session-data theft or page modification.
Summary
What happened
Stored XSS in saveuser.php in Traffic Offense Reporting System 1.0 allows remote authenticated users to run script in a viewer's browser. The handler inserts user_id, username, email, name, and position POST values into the database without sanitization, and view-users.php renders them without output encoding. A valid session is required to submit the add-user form, and the payload executes when another user opens the user list, enabling session-data theft or page modification.
The record
- CVE
- CVE-2025-5651
- Published
- Jun 5, 2025
- Updated
- Jun 5, 2025
- Vendor
- Code Projects
- Product
- Traffic Offense Reporting System
- Classifications
- CWE-94, CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 5, 2025CVE publishedPublication date reported by the CVE source.
- Jun 5, 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?
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
- Traffic Offense Reporting System saveuser.php stored 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