CVE-2025-15169VulnerabilityPublished 29 Dec 2025Updated 24 Feb 2026

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

Affects BiggiDroid Simple PHP CMSSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score

5.1Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 36% 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 29 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 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 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

To mitigate CVE-2025-15169, organizations should first restrict access to the /admin/editsite.php functionality to trusted administrators only, implementing strong authentication and network segmentation to reduce exposure. Code-level mitigation involves reviewing and refactoring the vulnerable code to use parameterized queries or prepared statements, ensuring all user inputs are properly sanitized and validated. Regularly auditing and monitoring logs for suspicious activity related to the editsite.php endpoint is critical. Organizations should also consider migrating to alternative CMS platforms with active vendor support or newer versions if available. Finally, enforcing the principle of least privilege for admin accounts and using multi-factor authentication can reduce the risk of exploitation by compromised credentials.

Description

A weakness has been identified in BiggiDroid Simple PHP CMS 1.0. Affected by this issue is some unknown functionality of the file /admin/editsite.php. Executing a manipulation of the argument ID can lead to sql injection. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The SQL injection vulnerability in BiggiDroid Simple PHP CMS 1.0 can have serious consequences for organizations using this software. Successful exploitation can lead to unauthorized access to sensitive data stored in the CMS database, including potentially user credentials, site content, or configuration details. Attackers could modify or delete data, undermining data integrity and availability of the CMS. This could disrupt website operations, damage organizational reputation, and lead to regulatory compliance issues if sensitive data is exposed. Since the vulnerability requires authenticated access with high privileges, insider threats or compromised admin accounts pose a significant risk. The availability of public exploit code increases the likelihood of exploitation attempts, especially in environments where patching or mitigation is delayed. Organizations relying on this CMS for critical web presence or data management are at risk of targeted attacks, data breaches, and service disruptions.

Summary

CVE-2025-15169 is a SQL injection vulnerability identified in BiggiDroid Simple PHP CMS version 1.0, located in the /admin/editsite.php script. The issue stems from insufficient input validation or sanitization of the 'ID' parameter, which is used in SQL queries without proper escaping or parameterization. This flaw allows an authenticated attacker with high privileges to inject malicious SQL code remotely, potentially manipulating the backend database. The vulnerability does not require user interaction but does require the attacker to be authenticated with elevated privileges, which limits the attack surface but still poses a significant risk. The vendor was notified early but has not issued any patches or responses, and public exploit code has been released, increasing the likelihood of exploitation attempts. The CVSS v4.0 base score is 5.1 (medium severity), reflecting the moderate impact and exploitation complexity. The vulnerability can lead to unauthorized data disclosure, data modification, or denial of service by corrupting database contents or disrupting CMS operations. No known active exploitation in the wild has been reported to date. Organizations running this CMS should consider immediate mitigation steps or migration, as the lack of vendor response leaves systems exposed.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats