Skip to content
Fencer Vulns
medium 5.3

CVE-2022-23513 json

Pi-Hole/AdminLTE vulnerable due to improper access control in queryads endpoint

published 2022-12-22 3 y ago modified 2026-06-17 4 mo ago also EUVD-2022-28554

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
42.3%
EPSS 42.3% chance of exploitation in 30 days, percentile 98%
public exploits
1
Exploit-DB

Summary

Pi-Hole is a network-wide ad blocking via your own Linux hardware, AdminLTE is a Pi-hole Dashboard for stats and more. In case of an attack, the threat actor will obtain the ability to perform an unauthorized query for blocked domains on `queryads` endpoint. In the case of application, this vulnerability exists because of a lack of validation in code on a root server path: `/admin/scripts/pi-hole/phpqueryads.php.` Potential threat actor(s) are able to perform an unauthorized query search in blocked domain lists. This could lead to the disclosure for any victims' personal blacklists.

Patch / fix

Timeline

  1. Published
  2. First public exploit (EDB-51705)

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
partial
Assessed
18 mo ago

Exploit prediction

42.25% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-51705 AdminLTE PiHole 5.18 - Broken Access Control webapps, 2023-09-04
  • github.com https://github.com/pi-hole/AdminLTE/security/advisories/GHSA-6qh8-6rrj-7497 referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/174460/AdminLTE-PiHole-Broken-Access-Control.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected products

  • pi-hole AdminLTE

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.