dbcve.org
PanelApplication · Xiaopi

CVE-2026-5332

MEDIUM · 6.1 CVSS v3.1 Published 2026-04-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 vulnerability was identified in Xiaopi Panel 1.0.0. This vulnerability affects unknown code of the file /demo.php of the component WAF Firewall. The manipulation of the argument param leads to cross site scripting. Remote exploitation of the attack is possible. The exploit is publicly available and might be used. 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 cross-site scripting (XSS) vulnerability in Xiaopi Panel 1.0.0 allows remote attackers to inject malicious scripts via the 'param' argument in the /demo.php file of the WAF Firewall component. The vulnerable parameter is reflected in the HTTP response without proper sanitization or output encoding.

MitigationImplement proper input validation and output encoding for the 'param' parameter in /demo.php. Use context-appropriate encoding (HTML entity encoding for HTML context) and consider implementing Content Security Policy headers as defense-in-depth.

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:= 1.0.0

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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
    Identify whether Xiaopi Panel web application is present on the server by locating its web root directory or checking for characteristic files such as index.php, admin files, or configuration files associated with Xiaopi Panel.
    Affected if Xiaopi Panel is installed on the system
  2. Verify exact version 1.0.0
    Locate the version information for the Xiaopi Panel installation. Check version files, headers, or the application itself to confirm the installed version is exactly 1.0.0.
    Affected if The installed version is 1.0.0
  3. Locate the /demo.php file in WAF Firewall component
    Search for the demo.php file within the WAF Firewall component directory under the Xiaopi Panel web root. The path typically follows a pattern such as /waf/demo.php or similar within the application structure.
    Affected if The file /demo.php exists in the WAF Firewall component directory
  4. Test param parameter for reflected input
    Send an HTTP request to /demo.php with a test value in the 'param' parameter (for example: ?param=<script>alert(1)</script>) and examine the HTTP response to see if the value is reflected without HTML encoding.
    Affected if The 'param' parameter value is reflected in the response without proper HTML entity encoding
  5. Confirm WAF Firewall component is accessible
    Verify that the /demo.php endpoint is reachable via HTTP/HTTPS from a client perspective. Check if network access restrictions or authentication requirements allow or block access to this file.
    Affected if The /demo.php endpoint is externally accessible without authentication

A user is affected if they have Xiaopi Panel version 1.0.0 installed with the accessible /demo.php file in the WAF Firewall component where the 'param' parameter reflects input unencoded.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding for the 'param' parameter in /demo.php. Use context-appropriate encoding (HTML entity encoding for HTML context) and consider implementing Content Security Policy headers as defense-in-depth.

Fix this in Panel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5332 — 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-5332 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