CVE-2025-51626
BaseFortify
Publication date: 2026-01-09
Last updated on: 2026-01-09
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| unknown_vendor | pss.sale.com | 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
Can you explain this vulnerability to me?
CVE-2025-51626 is a remote SQL injection vulnerability in version 1.0 of pss.sale.com. It occurs because the 'id' parameter in the /userfiles/php/cancel_order.php script does not properly filter or sanitize input. This allows attackers to inject arbitrary SQL commands remotely, potentially leading to unauthorized access to database information and possibly remote code execution on the affected system. [1]
How can this vulnerability impact me? :
This vulnerability can allow remote attackers to execute arbitrary SQL commands via the 'id' parameter, which may result in unauthorized disclosure of sensitive information from the database. Additionally, it could enable attackers to execute remote code on the affected system, compromising system integrity and security. [1]
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 /userfiles/php/cancel_order.php endpoint for SQL injection. You can use tools like sqlmap or manual curl commands to inject SQL payloads and observe the responses. For example, a curl command to test might be: curl 'http://your-target.com/userfiles/php/cancel_order.php?id=1' and then try injecting SQL such as 'id=1 OR 1=1'. Monitoring web server logs for suspicious requests to this endpoint with unusual parameter values can also help detect exploitation attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing proper input validation and sanitization on the 'id' parameter in the /userfiles/php/cancel_order.php script to prevent SQL injection. Applying parameterized queries or prepared statements is recommended. Additionally, restricting access to this endpoint and monitoring for suspicious activity can help reduce risk until a patch or update is applied. [1]