CVE-2025-15496
BaseFortify
Publication date: 2026-01-09
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 |
|---|---|---|
| guchengwuyue | yshopmall | to 1.9.1 (inc) |
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-15496 is an SQL injection vulnerability in the yshopmall application (up to version 1.9.1) that arises from improper handling of the 'sort' parameter in pageable requests. This parameter is passed unchecked into the SQL query's ORDER BY clause within the getPage function of the /api/jobs endpoint, allowing attackers to inject malicious SQL code. The vulnerability affects multiple REST controller endpoints and enables attackers to manipulate SQL queries, potentially leading to unauthorized data access or database compromise. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing remote attackers to execute arbitrary SQL commands on the affected system without authentication. This can lead to unauthorized access to sensitive data, modification or deletion of data, and potential compromise of the database's integrity and availability. The exploitation of this vulnerability can result in data breaches, loss of data integrity, and disruption of services. [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 /api/jobs endpoint for SQL injection via the 'sort' parameter. A common approach is to send crafted HTTP GET requests manipulating the 'sort' parameter to include SQL injection payloads and observe the response for errors or unexpected behavior. For example, using curl: curl -X GET 'http://<target>/api/jobs?sort=id' -H 'Authorization: Bearer <token>' and then modifying the 'sort' parameter to include SQL injection payloads such as 'id; DROP TABLE users;--' or similar. Monitoring logs for unusual SQL errors or anomalies related to the 'sort' parameter in requests can also help detect exploitation attempts. Automated vulnerability scanners that test for SQL injection on REST endpoints can be used as well. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include avoiding use of the affected versions of yshopmall (up to 1.9.1) or replacing the affected product, as no official patches or vendor responses are available yet. Restrict access to the /api/jobs endpoint to trusted users or networks, implement web application firewall (WAF) rules to detect and block SQL injection attempts targeting the 'sort' parameter, and monitor for suspicious activity. Input validation and sanitization on the 'sort' parameter should be implemented if possible. Since the vendor has not provided fixes, consider disabling or restricting the vulnerable functionality until a patch or update is available. [2]