VulnerabilityPublished 27 Oct 2025

CVE-2025-12201: ajayrandhawa User-Management-PHP-MYSQL · Unrestricted Upload

Affects ajayrandhawa User-Management-PHP-MYSQLSource CVE Database V5

Public exploit available · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

European organizations should implement strict access controls to limit high privilege user accounts and enforce strong authentication mechanisms, including multi-factor authentication, to reduce the risk of credential compromise. Input validation and sanitization should be applied rigorously on all file upload parameters, especially the 'image' argument in /admin/edit-user.php, to restrict file types, sizes, and content. Web application firewalls (WAFs) can be configured to detect and block suspicious file upload attempts. Monitoring and logging of file upload activities should be enhanced to detect anomalous behavior promptly. Organizations should consider isolating the user management application in a segmented network zone to limit lateral movement in case of compromise. Regular security audits and penetration testing focused on file upload mechanisms are recommended. Finally, organizations should maintain an incident response plan to quickly address any exploitation attempts.

Description

A vulnerability was identified in ajayrandhawa User-Management-PHP-MYSQL up to fedcf58797bf2791591606f7b61fdad99ad8bff1. This affects an unknown part of the file /admin/edit-user.php of the component User Management Interface. Such manipulation of the argument image leads to unrestricted upload. It is possible to launch the attack remotely. The exploit is publicly available and might be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, exploitation of this vulnerability could lead to unauthorized file uploads, enabling attackers to execute arbitrary code, implant malware, or disrupt services. This can compromise the confidentiality and integrity of sensitive user data managed by the application, potentially leading to data breaches and regulatory non-compliance under GDPR. The availability of the user management system could also be affected, disrupting internal operations or customer-facing services. Organizations in sectors such as finance, healthcare, government, and critical infrastructure that rely on PHP-MySQL based user management solutions are particularly at risk. The requirement for high privilege access somewhat limits the threat to insiders or attackers who have already compromised credentials, but the presence of public exploits increases the urgency for mitigation. The lack of vendor response and patches complicates remediation efforts, potentially prolonging exposure. Additionally, the rolling release nature of the product may cause challenges in tracking and applying updates, increasing the window of vulnerability.

Summary

CVE-2025-12201 is a vulnerability found in the ajayrandhawa User-Management-PHP-MYSQL software, specifically in the user management interface file /admin/edit-user.php. The flaw arises from improper validation of the 'image' parameter, allowing an attacker with high-level privileges to upload arbitrary files without restriction. This unrestricted upload vulnerability can be exploited remotely, potentially enabling attackers to upload malicious scripts or executables that could lead to remote code execution, privilege escalation, or persistent backdoors. The vulnerability does not require user interaction but does require the attacker to have authenticated access with high privileges, which limits the attack surface but still poses significant risk if credentials are compromised or insider threats exist. The product uses a rolling release model, making it difficult to identify specific affected versions or patches, and the vendor has not responded to vulnerability disclosure efforts. The CVSS 4.0 score is 5.1 (medium severity), reflecting network attack vector, low complexity, no user interaction, but requiring high privileges and resulting in low confidentiality, integrity, and availability impacts. No known exploits in the wild have been reported yet, but public exploit code is available, increasing the risk of future exploitation. The vulnerability highlights the importance of secure file upload handling and access control in web-based user management systems.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 3 Nov 2025, 06:11 UTC

Technical details

References

Community reviews

Related threats