CVE-2025-6356
BaseFortify
Publication date: 2025-06-20
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-6356 is a critical SQL injection vulnerability in the Simple Pizza Ordering System version 1.0, specifically in the /addmem.php file. It occurs because the application does not properly validate or sanitize the 'firstname' user input parameter, 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? :
Exploiting this vulnerability can lead to unauthorized database access, data leakage, modification, or deletion of data, and potentially full system compromise or service disruption. Attackers can remotely execute malicious SQL commands without authentication, impacting 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 vulnerability can be detected by identifying if the vulnerable file /addmem.php is accessible and if it processes the 'firstname' parameter without proper validation. One detection method is to use Google Hacking with the query "inurl:addmem.php" to find potentially vulnerable targets. Additionally, testing the /addmem.php endpoint with SQL injection payloads in the 'firstname' parameter can help confirm the vulnerability. For example, using curl or similar tools to send requests with SQL injection strings and observing the response can indicate vulnerability. Example command: curl -X POST -d "firstname=' OR '1'='1" http://targetsite.com/addmem.php [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements to handle SQL queries safely, enforcing strict input validation and filtering on the 'firstname' parameter to ensure it conforms to expected formats, and minimizing database user permissions by avoiding the use of high-privilege accounts for routine operations. Conducting regular security audits to detect and address vulnerabilities promptly is also recommended. If possible, replacing the affected component with an alternative product is advised. [2, 3]