dbcve.org
PanelApplication · Xiaopi

CVE-2026-2122

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-08
Fix available
A fix is available. Upgrade to after 2026-01-26 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A SQL injection vulnerability exists in the WAF Firewall component of Xiaopi Panel (up to version 20260126) in the /demo.php file. The ID parameter is not properly sanitized, allowing remote attackers to inject arbitrary SQL queries. The exploit is publicly available, increasing exploitation risk.

MitigationSince the vendor did not respond, immediately disable or restrict access to the /demo.php file, implement proper input validation and parameterized queries for the ID parameter, or deploy a WAF rule to block SQL injection attempts until a vendor patch is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PanelApplication
Affected:<= 2026-01-26

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Xiaopi Panel installation
    Locate the panel installation directory - common paths include /var/www/, /home/, or the web root. Look for Xiaopi Panel-specific files or directories.
    Affected if Xiaopi Panel software is not present on the system, then the CVE does not apply.
  2. Check for vulnerable /demo.php file
    Search for the demo.php file within the Xiaopi Panel web directory. Common paths: <web_root>/demo.php or <panel_dir>/demo.php.
    Affected if The file /demo.php does not exist, then the vulnerability is not present.
  3. Verify Xiaopi Panel version
    Check the panel version file or header - typically found in version.php, config files, or the admin interface. Compare the installed version to the affected range: <= 2026-01-26.
    Affected if The installed version is newer than 2026-01-26, then the system is not affected by this specific CVE.
  4. Confirm WAF Firewall component is active
    Access the Xiaopi Panel admin interface and navigate to the WAF Firewall settings, or inspect the configuration files for the WAF module status.
    Affected if The WAF Firewall component is disabled or not configured, then the SQL injection may not be reachable even if the vulnerable file exists.
  5. Inspect ID parameter handling in demo.php
    Examine the source code of /demo.php - specifically look for SQL queries that incorporate the 'ID' parameter without proper sanitization, parameterization, or prepared statements.
    Affected if The ID parameter is used in SQL queries without parameterized queries or input validation, then the system is vulnerable to SQL injection.

A system is affected if it runs Xiaopi Panel version <= 2026-01-26 with the /demo.php file present and the WAF Firewall component enabled, where the ID parameter lacks parameterized query implementation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 2026-01-26
Interim mitigation

Since the vendor did not respond, immediately disable or restrict access to the /demo.php file, implement proper input validation and parameterized queries for the ID parameter, or deploy a WAF rule to block SQL injection attempts until a vendor patch is available.

Fix this in Panel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2122 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2122 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data