CVE-2025-14652
BaseFortify
Publication date: 2025-12-14
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 |
|---|---|---|
| facebook-adrianmercurio | online_cake_ordering_system | 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?
CVE-2025-14652 is a critical SQL injection vulnerability in the Online Cake Ordering System version 1.0, specifically in the file admindetail.php when accessed with the parameters action=edit and the id argument. The vulnerability occurs because the id parameter is not properly validated or sanitized before being used in SQL queries, allowing attackers to inject malicious SQL code. This can lead to unauthorized database access, data leakage, data tampering, and potentially full system control. Exploitation does not require authentication and can be performed remotely using various SQL injection techniques such as Boolean-based blind, error-based, time-based blind, and UNION-based injections. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive information, modification or deletion of data, and disruption of service. Attackers can gain full control over the system remotely without needing any authentication, which can compromise the confidentiality, integrity, and availability of the system and its data. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the vulnerable parameter 'id' in the URL /cakeshop/admindetail.php?action=edit for SQL injection payloads. Example commands include using sqlmap to automate detection: `sqlmap -u "http://target/cakeshop/admindetail.php?action=edit&id=23" --batch` or manual testing with payloads such as `id=23 AND 3234=3234` (Boolean-based), `id=23 AND (SELECT 9820 FROM (SELECT(SLEEP(5)))fQWm)` (time-based), or UNION-based payloads like `id=23 UNION ALL SELECT NULL,NULL,NULL,NULL,CONCAT(...)`. These tests help confirm if the parameter is vulnerable by observing responses or delays. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Apply strict input validation and filtering to ensure the 'id' parameter only accepts expected formats (e.g., numeric). 3) Minimize database user permissions to avoid using high-privilege accounts for routine operations. 4) Conduct regular security audits to detect and fix vulnerabilities promptly. If possible, consider replacing the affected component with a secure alternative. [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized access, modification, and leakage of sensitive data through SQL injection, which can lead to violations of data protection regulations such as GDPR and HIPAA. Exploitation of this flaw compromises confidentiality, integrity, and availability of data, potentially resulting in non-compliance with these standards that require protection of personal and sensitive information. Immediate remediation is critical to maintain compliance and protect data integrity. [1, 2, 3]