Unauthenticated name changes via client-supplied username
Published Apr 6, 2026 · Updated Apr 6, 2026
Improper authorization in Cyber-III Student Management System allows remote attackers to change another user's displayed name. The /viva/update.php handler accepts client-supplied username and name values, then updates the matching team_members row without checking a session or authorization. An unauthenticated POST request and knowledge of an existing username are sufficient; the demonstrated consequence is unauthorized modification of that account's name.
Summary
What happened
Improper authorization in Cyber-III Student Management System allows remote attackers to change another user's displayed name. The /viva/update.php handler accepts client-supplied username and name values, then updates the matching team_members row without checking a session or authorization. An unauthenticated POST request and knowledge of an existing username are sufficient; the demonstrated consequence is unauthorized modification of that account's name.
The record
- CVE
- CVE-2026-5642
- Published
- Apr 6, 2026
- Updated
- Apr 6, 2026
- Vendor
- Cyber-III
- Product
- Student Management System
- Classifications
- CWE-266, CWE-285, T1190, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 6, 2026CVE publishedPublication date reported by the CVE source.
- Apr 6, 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=1a938fa61e9f735078e9b291d2e6215b4942af3f
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 #236 HTTP POST proof of conceptfunctional · 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