CVE-2025-15169
SQL Injection in BiggiDroid Simple PHP CMS /admin/editsite.php
Publication date: 2025-12-29
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| biggidroid | simple_php_cms | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a SQL injection issue in BiggiDroid Simple PHP CMS 1.0, specifically in the /admin/editsite.php file. By manipulating the ID argument, an attacker can execute unauthorized SQL commands remotely, potentially compromising the database.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to manipulate the database through SQL injection, leading to unauthorized access, data leakage, data modification, or disruption of service. This can compromise the confidentiality, integrity, and availability of the affected system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows SQL injection attacks that can compromise the confidentiality, integrity, and availability of the system, potentially leading to unauthorized access or manipulation of sensitive data. Such breaches could result in non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information. However, no specific details about compliance impact or mitigation measures are provided in the available resources. [1, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the presence of the vulnerable endpoint /admin/editsite.php and testing the 'ID' parameter for SQL injection. One method is to use Google dorking with the query: inurl:admin/editsite.php to locate potentially vulnerable targets. For direct testing, you can use tools like curl or sqlmap to send crafted requests to the 'ID' parameter and observe if SQL injection is possible. Example command with sqlmap: sqlmap -u "http://target/admin/editsite.php?ID=1" --batch --dbs. Alternatively, manual testing can be done by appending SQL injection payloads to the ID parameter and checking for database errors or unexpected behavior. [1]
What immediate steps should I take to mitigate this vulnerability?
No known countermeasures or mitigations have been published by the vendor, and the vendor did not respond to early disclosure attempts. Immediate steps include restricting access to the /admin/editsite.php endpoint to trusted users only, applying web application firewall (WAF) rules to detect and block SQL injection attempts targeting the 'ID' parameter, and monitoring logs for suspicious activity. Additionally, avoid exposing the vulnerable CMS to the public internet until a patch or fix is available. If possible, review and sanitize input handling in the source code to prevent SQL injection by using parameterized queries or prepared statements. [1]