CVE-2026-2122VulnerabilityPublished 8 Feb 2026Updated 23 Feb 2026

CVE-2026-2122: Xiaopi Panel · SQL Injection

Affects Xiaopi PanelSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 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 23% 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 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

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 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
XiaopiPanel	Affected =20260126	Fixed in–
GitHubltranquility/CVE`pkg:github/ltranquility/CVE`Other threats	Affected =20260126	Fixed in–

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

AI-suggested

1. Immediately restrict external access to the /demo.php endpoint or the entire Xiaopi Panel interface via network controls such as firewalls or VPNs to limit exposure. 2. Implement web application firewall rules to detect and block SQL injection patterns targeting the 'ID' parameter. 3. Employ input validation and parameterized queries or prepared statements if modifying the source code is possible to prevent injection. 4. Monitor logs for suspicious database query patterns or unusual activity related to the 'ID' parameter. 5. If feasible, isolate the affected Xiaopi Panel instance in a segmented network zone to reduce potential lateral movement. 6. Engage with the vendor or community to obtain patches or updated versions addressing the vulnerability. 7. Consider deploying runtime application self-protection (RASP) tools to detect and block injection attempts dynamically. 8. Prepare incident response plans to quickly address potential exploitation attempts given the public availability of exploits.

Description

A security flaw has been discovered in Xiaopi Panel up to 20260126. This impacts an unknown function of the file /demo.php of the component WAF Firewall. The manipulation of the argument ID results in sql injection. The attack may be launched remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The SQL injection vulnerability in Xiaopi Panel can allow attackers to execute arbitrary SQL commands on the backend database, potentially leading to unauthorized data disclosure, data manipulation, or deletion. This compromises the confidentiality, integrity, and availability of the affected systems. Exploitation can result in leakage of sensitive information, unauthorized privilege escalation, or disruption of services relying on the database. Since the attack can be launched remotely without authentication, the attack surface is broad, increasing the risk to organizations using Xiaopi Panel. The public availability of exploit code further elevates the threat, potentially enabling automated attacks. Organizations relying on Xiaopi Panel for web application firewall functionality may face increased risk of compromise, data breaches, and operational disruption until the vulnerability is remediated.

Summary

CVE-2026-2122 identifies a SQL injection vulnerability in Xiaopi Panel up to version 20260126, specifically within the /demo.php file of the WAF Firewall component. The vulnerability stems from inadequate input validation of the 'ID' parameter, which allows an attacker to inject arbitrary SQL commands remotely without requiring authentication or user interaction. This flaw can be exploited to manipulate backend database queries, potentially leading to unauthorized data access, modification, or deletion. The vulnerability has a CVSS 4.0 score of 5.3, reflecting medium severity due to the partial impact on confidentiality, integrity, and availability, and the lack of required privileges or user interaction. The vendor was notified but has not issued a patch or response, and public exploit code is available, increasing the risk of exploitation in the wild. The vulnerability affects only the specified version 20260126 of Xiaopi Panel, and no known exploits have been observed in the wild yet. The lack of vendor response and patch availability necessitates immediate defensive measures by users of the affected product.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 21:30 UTC

Technical details

References

Community reviews

Related threats