CVE-2025-15263VulnerabilityPublished 30 Dec 2025Updated 24 Feb 2026

CVE-2025-15263: BiggiDroid Simple PHP CMS · SQL Injection

Affects BiggiDroid Simple PHP CMSSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

6.9Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
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 30 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

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 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

Affected software

Product	Affected	Fixed in
Packagistbiggidroid/simple-php-cms`pkg:composer/biggidroid/simple-php-cms`Other threats	Affected =1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate mitigation should include restricting access to the /admin/login.php page via IP whitelisting or VPN to limit exposure to trusted users only. 2. Implement web application firewall (WAF) rules specifically designed to detect and block SQL injection patterns targeting the Username parameter. 3. Apply strict input validation and sanitization on all user inputs, especially the Username field, using parameterized queries or prepared statements to prevent injection. 4. Monitor logs for unusual login attempts or SQL error messages that may indicate exploitation attempts. 5. Conduct a thorough security audit of the CMS codebase to identify and remediate other potential injection points. 6. If available, apply official patches or updates from BiggiDroid promptly once released. 7. Consider migrating to a more secure or actively maintained CMS platform if no timely patch is forthcoming. 8. Educate administrators on secure password policies and multi-factor authentication to reduce risk if credentials are compromised. 9. Regularly back up CMS data and configurations to enable recovery in case of compromise. 10. Engage in threat intelligence sharing to stay informed about emerging exploits targeting this vulnerability.

Description

A weakness has been identified in BiggiDroid Simple PHP CMS 1.0. Affected is an unknown function of the file /admin/login.php of the component Admin Login. Executing a manipulation of the argument Username can lead to sql injection. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks.

Impact

The impact of CVE-2025-15263 on organizations worldwide can be significant, particularly for those using BiggiDroid Simple PHP CMS version 1.0. Exploitation could lead to unauthorized access to the CMS administrative interface, enabling attackers to manipulate website content, steal sensitive user data, or deploy further malware. Data confidentiality is at risk due to potential unauthorized data extraction. Integrity could be compromised by unauthorized modification or deletion of database records. Availability might be affected if attackers disrupt CMS operations or delete critical data. Since the vulnerability requires no authentication or user interaction, it can be exploited remotely and at scale, increasing the risk of widespread compromise. Organizations relying on this CMS for business-critical websites or services may face reputational damage, regulatory penalties, and operational disruptions. The public disclosure of exploit code further elevates the threat level by lowering the barrier for attackers to conduct automated or targeted attacks.

Summary

CVE-2025-15263 identifies a SQL injection vulnerability in BiggiDroid Simple PHP CMS version 1.0, specifically within the /admin/login.php file's Username parameter. The vulnerability arises due to improper sanitization or validation of user-supplied input, allowing an attacker to inject malicious SQL code into backend database queries. This injection can be performed remotely without requiring authentication or user interaction, making exploitation relatively straightforward. The flaw affects the Admin Login component, which is critical as it controls access to the CMS backend. Successful exploitation could allow attackers to bypass authentication, extract sensitive data such as user credentials, modify or delete database records, or potentially execute administrative commands depending on the database privileges. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P) indicates network attack vector, low attack complexity, no privileges or user interaction needed, and partial impacts on confidentiality, integrity, and availability. Although no confirmed exploits are reported in the wild, the public availability of exploit code increases the likelihood of attacks. No official patches or updates have been linked yet, so mitigation currently relies on defensive coding practices and access controls. This vulnerability highlights the risks of insufficient input validation in web applications, especially in authentication modules.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 22:45 UTC

Technical details

References

Community reviews

Related threats