VulnerabilityPublished 11 Mar 2026

CVE-2026-3957: xierongwkhd weimai-wetapp · SQL Injection

Affects xierongwkhd weimai-wetappSource CVE Database V5

Compare

Public exploit available · CVSS 5.1 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

5.1Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/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: High
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: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
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 11 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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
xierongwkhdweimai-wetapp	Affected =5fe9e8225be4f73f2c5087f134aff657bdf1c6f2	Fixed in–

AI-suggested

Organizations should immediately audit and restrict access to the weimai-wetapp application, ensuring only trusted users have high privileges. Implement strict input validation and parameterized queries or prepared statements in the getLikeMovieList function to prevent SQL injection. Conduct thorough code reviews focusing on all database interaction points. Monitor logs for unusual database query patterns or failed injection attempts. Employ web application firewalls (WAFs) with custom rules to detect and block SQL injection payloads targeting the 'cat' parameter. Engage with the vendor or community for updates and patches. Plan for rapid deployment of fixes once available, and maintain an incident response plan for potential exploitation.

Description

CVE-2026-3957 is a medium severity SQL injection vulnerability found in the xierongwkhd weimai-wetapp product, specifically in the getLikeMovieList function of HomeController.java. The flaw allows remote attackers to manipulate the 'cat' argument to execute SQL injection attacks without requiring user interaction but requiring high privileges. The vulnerability affects versions up to commit 5fe9e8225be4f73f2c5087f134aff657bdf1c6f2. Although an exploit has been published, no known active exploitation in the wild has been reported yet. The vendor has not responded to the early report, and no patch is currently available. The rolling release model complicates version tracking and patch deployment. Organizations using this product should prioritize code review and input validation to mitigate risk.

Impact

The SQL injection vulnerability can lead to unauthorized access to sensitive data, data corruption, or deletion within the affected database. Attackers with high privileges can leverage this flaw to escalate their access, potentially compromising the entire application backend and connected systems. This can result in data breaches, loss of data integrity, and service disruptions. Organizations using weimai-wetapp in critical environments may face operational downtime, reputational damage, and regulatory compliance issues. The rolling release nature of the product complicates timely patching, increasing exposure duration. Since exploitation requires high privileges, the threat is somewhat contained but still significant in environments where insider threats or compromised accounts exist. The published exploit increases the risk of opportunistic attacks once attackers gain sufficient access.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Mar 2026, 02:29 UTC

Technical details

References

Community reviews

Related threats