CVE-2025-14832
BaseFortify
Publication date: 2025-12-17
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-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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a SQL injection in the itsourcecode Online Cake Ordering System 1.0, specifically in the /updateproduct.php?action=edit file. Manipulating the ID argument allows an attacker to inject SQL code, potentially compromising the database. The attack can be launched remotely and an exploit is publicly available.
How can this vulnerability impact me? :
The vulnerability can allow attackers to execute arbitrary SQL commands on the database, which may lead to unauthorized data access, data modification, or deletion. This can compromise the integrity, confidentiality, and availability of the system's data.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /cakeshop/updateproduct.php endpoint with the parameters action=edit and id=1001 for SQL injection. Tools like sqlmap can be used to confirm the vulnerability by crafting POST requests targeting parameters such as id, Productname, Quantity, Price, Markup, Selling, and code. Example command using sqlmap: sqlmap -u "http://target/cakeshop/updateproduct.php?action=edit&id=1001" --data="Productname=test&Quantity=1&Price=10&Markup=5&Selling=15&code=abc" --risk=3 --level=5 --batch. Additionally, manual testing using boolean-based blind SQL injection, error-based SQL injection, or time-based blind SQL injection techniques (e.g., injecting payloads that cause delays or errors) can help detect the issue. [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 inputs conform to expected formats. 3) Minimize database user permissions by avoiding use of high-privilege accounts like root or admin for routine operations. 4) Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly. If possible, consider replacing the affected product with a secure alternative. [1, 3]