CVE-2025-6481
BaseFortify
Publication date: 2025-06-22
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 |
|---|---|---|
| carmelo | simple_pizza_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?
CVE-2025-6481 is a critical SQL injection vulnerability in version 1.0 of the Simple Pizza Ordering System, specifically in the /update.php file. The vulnerability occurs because the 'id' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This can lead to unauthorized access to the database, enabling attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized database access, data leakage, data tampering, full system control by attackers, and potential service disruption. Since exploitation requires no authentication and can be done remotely, attackers can manipulate or delete data, compromise data integrity, and disrupt the availability of the system. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'id' parameter in the /update.php file for SQL injection. One method is to use time-based blind SQL injection payloads such as appending `id=12 AND (SELECT 9718 FROM (SELECT(SLEEP(5)))TQNc)` to the URL and observing delayed responses. Automated tools like sqlmap can be used to scan and confirm the presence of the SQL injection vulnerability by targeting the 'id' parameter in /update.php. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Applying strict input validation and filtering on the 'id' parameter to ensure it conforms to expected formats. 3) Limiting database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. 4) Conducting regular security audits of code and systems to detect and fix vulnerabilities promptly. Additionally, replacing the affected software with a secure alternative is recommended since no known countermeasures are documented. [2, 3]