CVE-2024-58316
BaseFortify
Publication date: 2025-12-12
Last updated on: 2025-12-19
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| puneethreddyhc | online_shopping_system_advanced | 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. |
Attack-Flow Graph
AI Powered Q&A
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 'cm' parameter in the payment_success.php script for SQL injection flaws. A common method is to use sqlmap with a crafted payload to check for time-based blind SQL injection. For example, you can run a command like: sqlmap -u "http://target/online-shopping-system-advanced/payment_success.php?st=Completed&cm=1" --risk=3 --level=5 --technique=T --dbms=MySQL --time-sec=5 to detect if the parameter is vulnerable. Additionally, manual testing can be done by injecting payloads such as: http://target/online-shopping-system-advanced/payment_success.php?st=Completed&cm=1' AND (SELECT SLEEP(5)) AND '1'='1 to observe if the response time increases, indicating vulnerability. [3]
How can this vulnerability impact me? :
The vulnerability can allow attackers to access sensitive database information without authorization. This can lead to data breaches, exposure of personal or financial data, and potential unauthorized actions within the system, compromising the security and integrity of the online shopping platform.
Can you explain this vulnerability to me?
This vulnerability is a SQL injection in the payment_success.php script of Online Shopping System Advanced 1.0. It occurs because the 'cm' parameter is not properly filtered, allowing attackers to inject malicious SQL code. By exploiting this, attackers can manipulate the user ID parameter to send crafted SQL queries and retrieve sensitive information from the database.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include sanitizing and validating the 'cm' parameter in the payment_success.php script to prevent SQL injection. Use prepared statements or parameterized queries instead of directly embedding user input into SQL queries. Additionally, restrict database permissions to limit the impact of any potential injection. Applying web application firewalls (WAF) rules to detect and block SQL injection attempts can also help mitigate exploitation while a permanent fix is developed. [2, 3]