CVE-2025-6482
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-6482 is a critical SQL injection vulnerability in the Simple Pizza Ordering System version 1.0, specifically in the /edituser-exec.php file. The vulnerability occurs because the 'userid' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, full system compromise, and potential service disruption. Attackers can manipulate or delete data, retrieve sensitive information, and potentially disrupt business continuity. Since exploitation requires no authentication and can be performed remotely, it poses a severe risk to system security. [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 'userid' parameter in the /edituser-exec.php file for SQL injection. A common method is to use time-based blind SQL injection payloads, such as injecting a delay using the SLEEP() function in MySQL. For example, sending a POST request with the payload: userid=8' AND (SELECT 9787 FROM (SELECT(SLEEP(5)))QkQw)-- TQap can confirm the vulnerability if the response is delayed. Tools like sqlmap can also be used to automate detection. Additionally, Google dorking with queries like "inurl:edituser-exec.php" can help identify vulnerable targets. [2, 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 to ensure inputs conform to expected formats. 3) Minimizing database user permissions by avoiding use of high-privilege accounts for routine operations. 4) Conducting regular security audits of code and systems to detect and remediate vulnerabilities promptly. If possible, replace the affected component with an alternative product. [2, 3, 1]