dbcve.org
Web InterfaceApplication · Pi Hole

CVE-2026-33404

MEDIUM · 6.1 CVSS v3.1 Published 2026-04-06
Fix available
A fix is available. Upgrade to after 6.4.1 or later.
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
Pi-hole Admin Interface is a web interface for managing Pi-hole, a network-level ad and internet tracker blocking application. From 6.0 to before 6.5, client hostnames and IP addresses from the FTL database are rendered into the DOM without escaping in network.js (Network page) and charts.js/index.js (Dashboard chart tooltips). While upstream validation in dnsmasq and FTL blocks HTML characters via normal DHCP/DNS paths, the web UI performs no output escaping — an inconsistency with other fields in the same file that are properly escaped. This vulnerability is fixed in 6.5.

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 · high confidence

This is a stored Cross-Site Scripting (XSS) vulnerability in Pi-hole Admin Interface where client hostnames and IP addresses from the FTL database are rendered into the DOM without output escaping in network.js (Network page) and charts.js/index.js (Dashboard chart tooltips). While upstream validation in dnsmasq and FTL blocks HTML characters via normal DHCP/DNS paths, the web UI fails to escape output, creating an inconsistency with other properly escaped fields.

MitigationUpgrade Pi-hole Admin Interface to version 6.5 or later to obtain the patched version with proper output escaping for client hostnames and IP addresses.

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
Web InterfaceApplication
Affected:>= 6.0, <= 6.4.1

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. Check Pi-hole Admin Interface version
    Access the web interface and look at the footer, or run `pihole -v` from command line to identify the installed web package version
    Affected if Version is 6.0, 6.1, 6.2, 6.3, 6.4, or 6.4.1 (any version from 6.0 through 6.4.1 inclusive)
  2. Verify FTL database contains client records
    Check if the FTL database (usually at /etc/pihole/pihole-FTL.db) contains entries in the network table that could contain client hostnames or IP addresses
    Affected if FTL database has client network records and the Admin Interface is accessible
  3. Confirm Network page is accessible
    Attempt to access the Network page in the Pi-hole Admin Interface (usually at /admin/network.php)
    Affected if The Network page is reachable and displays client hostnames/IPs from the FTL database
  4. Confirm Dashboard charts are accessible
    Access the Dashboard in the Pi-hole Admin Interface and verify chart tooltips display client information
    Affected if The Dashboard is reachable and displays charts with client data in tooltips

A user is affected if they run Pi-hole Admin Interface version 6.0 through 6.4.1 and have access to the Network page or Dashboard where client hostnames/IPs from the FTL database are displayed without escaping.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 6.4.1
Interim mitigation

Upgrade Pi-hole Admin Interface to version 6.5 or later to obtain the patched version with proper output escaping for client hostnames and IP addresses.

Recommended fix High confidence

6.5

  1. Ensure you have a backup of your Pi-hole configuration and data
  2. Update your package repositories to check for new packages
  3. Run the package manager upgrade command (e.g., `pihole -up` or `apt update && apt upgrade` depending on your installation method)
  4. Verify the Admin Web Interface has been upgraded to version 6.5
  5. Confirm the vulnerability is patched by checking the network.js and charts.js files now properly escape output

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Web Interface Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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