VulnerabilityPublished 9 Jan 2026Updated 23 Feb 2026

CVE-2025-15496: guchengwuyue yshopmall · SQL Injection

Affects guchengwuyue yshopmallSource CVE Database V5

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
guchengwuyueyshopmall	Affected =1.9.0 =1.9.1	Fixed in–
GitHubguchengwuyue/yshopmall`pkg:github/guchengwuyue/yshopmall`Other threats	Affected =1.9.0 =1.9.1	Fixed in–

CPE configurations (1)

cpe:2.3:a:guchengwuyue:yshopmall:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official patch is released, organizations should implement strict input validation and sanitization on the 'sort' parameter in the /api/jobs endpoint to prevent SQL injection. Employing parameterized queries or prepared statements in the codebase is critical to eliminate injection vectors. Web Application Firewalls (WAFs) should be configured to detect and block SQL injection patterns targeting this endpoint. Monitoring logs for unusual query patterns or errors related to the 'sort' parameter can help detect attempted exploitation. Restrict database user permissions to the minimum necessary to limit potential damage from injection attacks. Consider isolating or temporarily disabling the vulnerable API endpoint if feasible. Organizations should maintain an active vulnerability management process to apply patches promptly once available and keep abreast of vendor updates. Conducting penetration testing focused on injection flaws can help identify residual risks.

Description

A vulnerability was determined in guchengwuyue yshopmall up to 1.9.1. Affected is the function getPage of the file /api/jobs. This manipulation of the argument sort causes sql injection. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.

Impact

The SQL injection vulnerability in yshopmall can have significant consequences for organizations using the affected versions. Exploitation could allow attackers to extract sensitive customer data, including personal and payment information, leading to data breaches and regulatory non-compliance. Attackers might also alter or delete critical data, impacting business operations and data integrity. Additionally, crafted SQL injections could cause denial of service by disrupting database availability. Since the vulnerability is remotely exploitable without authentication, it broadens the attack surface and increases risk. E-commerce platforms are high-value targets due to the sensitive nature of stored data and their role in revenue generation, making this vulnerability particularly impactful for businesses relying on yshopmall. The absence of an official patch and public exploit disclosure further elevate the threat level.

Summary

CVE-2025-15496 identifies a SQL injection vulnerability in the yshopmall e-commerce platform developed by guchengwuyue, specifically affecting versions 1.9.0 and 1.9.1. The vulnerability resides in the getPage function of the /api/jobs API endpoint, where the 'sort' parameter is improperly sanitized, allowing an attacker to inject arbitrary SQL commands. This injection flaw enables remote attackers to manipulate backend database queries, potentially leading to unauthorized data access, data modification, or denial of service. The vulnerability requires no authentication or user interaction, increasing its risk profile. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P) indicates network attack vector, low attack complexity, no user interaction, and partial impact on confidentiality, integrity, and availability. No known exploits are currently active in the wild, but public disclosure increases the risk of exploitation. The lack of vendor response necessitates immediate mitigation by users of affected versions.

References

Community reviews

Loading reviews…