Incorrect authorization in PHPGurukul User Registration & Login and User Management System

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-105703?

CVE-2026-105703 is a vulnerability classified as Incorrect Authorization and Improper Authorization, affecting User Registration & Login and User Management System (affected versions: 3.3). This vulnerability is rated Medium, with a CVSS score of 5.1. Public exploit code or evidence is available for this vulnerability, but that does not confirm exploitation in the wild.

Overview

Original source data

A vulnerability was determined in PHPGurukul User Registration & Login and User Management System 3.3. The impacted element is an unknown function of the file loginsystem/admin/change-password.php of the component Change Password Handler. This manipulation of the argument currentpassword causes incorrect authorization. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized.

Affected products and scope

  • PHPGurukul User Registration & Login and User Management System 3.3 is identified as affected.
  • The affected component is the Change Password Handler in loginsystem/admin/change-password.php within the admin panel.
  • The record and consulted sources do not identify a fixed release, an unaffected parallel branch, or additional version boundaries. A different release should not be treated as safe solely because it exists.

Technical details

The flaw is in loginsystem/admin/change-password.php, part of the administrative Change Password Handler. The endpoint accepts the POST parameter currentpassword, but the current-password validation is not bound to the identity of the administrator in the active session. The public code analysis shows a validation query that searches for a matching password in the admin table, followed by an update that uses $_SESSION['adminid'] to change the password for the current session account. If multiple administrator accounts exist, a password belonging to another administrator can therefore satisfy the check and allow the active account password to be changed. This is an Incorrect Authorization issue corresponding to CWE-863 and CWE-285. The record does not identify the exact function, but it identifies the affected file, component, and parameter.

Exploitability

  • The endpoint is reachable over the network, but exploitation requires an authenticated administrative session; the flaw does not by itself provide initial login access.
  • The supplied assessment indicates high privileges are required, low attack complexity, and no interaction from another user.
  • Technical details and a public proof of concept are available. The PoC describes accessing the administrative area and submitting a request to the password-change function.
  • The record does not establish whether the public proof of concept has been used in real-world attacks.

Technical impact

  • The direct technical outcome is that re-authentication can accept a password belonging to another administrator while the update continues to target the account represented by the current session.
  • An attacker must already possess a valid administrative session or equivalent administrative privileges; the flaw has not been shown to bypass the initial login process.
  • Possible consequences include credential changes, loss of access for legitimate administrators, and persistence through a compromised administrative session.
  • The resulting data, functionality, and availability impact depends on the privileges of the active administrator and the application's configuration.

Business impact

  • An attacker who already controls an administrative session may change the password of the administrator account associated with that session without knowing that account's correct current password.
  • This can lock out a legitimate administrator and may allow continued access to an account whose session has been compromised.
  • The affected administrator may be able to modify user records and perform other administrative operations permitted by that account.
  • Actual data, service, and access consequences depend on the privileges of the affected administrator. The record does not show that the flaw alone provides initial access or proves a specific data breach.

Remediation

  1. Replace the affected deployment with an alternative product if the organization cannot modify the source; the available advisory does not identify a fixed release or an official mitigation.
  2. If replacement is not immediately possible, restrict the administrative panel to trusted networks or place it behind additional access controls. This is a compensating precaution, not a confirmed fix.
  3. Correct the Change Password Handler so the current-password query is bound to the session administrator's ID rather than accepting a match from any administrator record. Use a prepared statement when implementing the corrected logic.
  4. After correction or replacement, force administrator password changes, invalidate older administrative sessions, and review unexpected password changes. Treat the deployment as remediated only after verifying that one administrator's password cannot validate a different administrator's session.

Detection

  1. Inventory PHPGurukul deployments and identify loginsystem/admin/change-password.php in administrative areas.
  2. Review the Change Password Handler source to determine whether the currentpassword validation query is constrained by the session administrator ID or only searches for a matching password in the admin table.
  3. Confirm that a password update can affect only the administrator identified by the active session.
  4. In an authorized staging environment, test account binding without submitting another administrator's password to production.
  5. As a precaution, review web, application, and database audit logs for requests to the administrative password-change endpoint and unexpected password changes. The absence of suspicious log evidence does not prove that the deployment is safe.
Sources (18)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.