Overview
CVE-2025-50489 is a critical security vulnerability in PHPGurukul Student Result Management System v2.0. This vulnerability stems from improper session invalidation in the /srms/change-password.php component and can result in a session hijacking attack. It poses a significant risk to educational institutions and potentially students’ sensitive data, leading to potential system compromise or data leakage.
Vulnerability Summary
CVE ID: CVE-2025-50489
Severity: High (7.5)
Attack Vector: Network
Privileges Required: Low
User Interaction: Required
Impact: System compromise, potential data leakage
Affected Products
Share secrets securely
Ameeba is private infrastructure for communication and sensitive work built on encrypted identity instead of exposed corporate identity systems.
Passwords, credentials, confidential files, screenshots, internal discussions, sensitive AI context, and private coordination should not become exposed across ordinary communication platforms.
- • Encrypted identity
- • Private Spaces for organizations and teams
- • End-to-end encrypted chat, calls, files, and notes
- • Sensitive AI work and protected collaboration
- • Built for information that cannot leak
Our mission is to secure human work alongside AI.
Product | Affected Versions
PHPGurukul Student Result Management System | v2.0
How the Exploit Works
The exploit takes advantage of an improper session invalidation mechanism in the /srms/change-password.php component of the application. By manipulating the session tokens, an attacker could potentially hijack a user’s session. This could grant the attacker unauthorized access to the system under the guise of a legitimate user, leading to unauthorized data access or even system compromise.
Conceptual Example Code
Consider the following conceptual HTTP request that an attacker might use:
GET /srms/change-password.php?session_id=VULNERABLE_SESSION_ID HTTP/1.1
Host: target.example.eduIn this example, the attacker is attempting to access the change-password.php page using a session ID that they have either guessed, stolen, or otherwise obtained illicitly. If the session invalidation is not handled correctly, this could allow the attacker to hijack the session associated with that ID, effectively impersonating the legitimate user.