VulnerabilityPublished 8 Dec 2025

CVE-2025-14259: Jihai Jshop MiniProgram Mall System · SQL Injection

Affects Jihai Jshop MiniProgram Mall SystemSource 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.2% chance of exploitation in 30 days – higher than 13% 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 8 Dec 2025
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
Jihai Jshop MiniProgram Mall System	Affected =2.9.0	Fixed in–

AI-suggested

Immediate implementation of input validation and sanitization for the cat_id parameter to prevent SQL injection.
Refactor the affected code to use parameterized queries or prepared statements, eliminating direct concatenation of user input into SQL commands.
Deploy Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the vulnerable endpoint.
Restrict access to the /index.php/api.html endpoint via network segmentation or IP whitelisting where feasible.
Conduct thorough code audits and penetration testing to identify and remediate similar injection flaws in other parts of the application.
Monitor logs and network traffic for suspicious activities indicative of SQL injection exploitation attempts.
Engage with the vendor or community to seek official patches or updates and apply them promptly once available.
Consider migrating to alternative, actively maintained e-commerce platforms if vendor support remains absent.
Educate development teams on secure coding practices to prevent future injection vulnerabilities.
Backup databases regularly and ensure recovery procedures are tested to mitigate potential data loss from exploitation.

Description

A vulnerability was found in Jihai Jshop MiniProgram Mall System 2.9.0. Affected by this issue is some unknown functionality of the file /index.php/api.html. The manipulation of the argument cat_id results in sql injection. The attack may be launched remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations using Jihai Jshop MiniProgram Mall System 2.9.0, this vulnerability poses significant risks. Exploitation can lead to unauthorized disclosure of sensitive customer and business data, undermining confidentiality. Attackers could alter or delete critical e-commerce data, impacting data integrity and potentially causing financial losses or reputational damage. Availability may also be affected if attackers execute destructive SQL commands or cause database corruption. Given the public availability of exploit code and lack of vendor response, the threat of exploitation is elevated. Organizations with internet-facing instances are particularly vulnerable. The impact is amplified in sectors with stringent data protection regulations like GDPR, where breaches can result in heavy fines and legal consequences. Additionally, e-commerce platforms are attractive targets for cybercriminals aiming to steal payment information or disrupt business operations. The medium severity score suggests moderate but non-trivial risk, warranting prompt attention. Failure to address this vulnerability could lead to data breaches, loss of customer trust, and operational disruptions.

Summary

CVE-2025-14259 identifies a SQL injection vulnerability in Jihai Jshop MiniProgram Mall System version 2.9.0, specifically affecting the /index.php/api.html endpoint. The vulnerability arises from improper sanitization of the cat_id parameter, which an attacker can manipulate to inject malicious SQL queries. This injection flaw allows remote attackers to execute arbitrary SQL commands on the backend database without requiring authentication or user interaction, increasing the attack surface significantly. The vulnerability has a CVSS 4.0 base score of 5.3, classified as medium severity, reflecting moderate impact and ease of exploitation. The vendor was notified but has not issued a patch or response, and public exploit code is available, which raises the risk of active exploitation. The flaw can lead to unauthorized data access, modification, or deletion, potentially compromising confidentiality, integrity, and availability of the affected systems. Since the vulnerability is in an e-commerce mini program system, attackers could extract sensitive customer data, manipulate product listings, or disrupt service availability. The lack of authentication requirement and remote exploitability make this a critical concern for organizations running this software, especially if exposed to the internet. The vulnerability's exploitation does not require user interaction, further simplifying attack execution. No official patches or mitigations have been released, increasing urgency for organizations to implement compensating controls.

References

Community reviews

Loading reviews…