CVE-2024-44069VulnerabilityPublished 19 Aug 2024Updated 29 Oct 2024

CVE-2024-44069: web · n/a

Affects webSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 6 soon.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Aug 2024
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-26.

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

Upgrade pi-hole/web to 6.

Affected software

Product	Affected	Fixed in
GitHubpi-hole/web`pkg:github/pi-hole/web`Other threats	Affected <6	Fixed in 6

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

AI-suggested

If you cannot patch yet, organizations should consider the following mitigations: 1) Restrict network access to the Pi-hole web interface by limiting it to trusted IP addresses or VPN access only, preventing unauthorized external access to the API endpoint. 2) Implement web application firewall (WAF) rules to detect and block requests to admin/api.php with the setTempUnit parameter from untrusted sources. 3) Monitor Pi-hole logs for unusual or repeated requests to the temperature unit setting endpoint to detect potential exploitation attempts. 4) Review and harden Pi-hole configuration and access controls, ensuring that the dashboard is not exposed to the public internet. 5) Stay informed on vendor updates and apply patches promptly once available. 6) Consider deploying network segmentation to isolate Pi-hole servers from general user networks to reduce attack surface. These steps go beyond generic advice by focusing on access control and monitoring specific to the vulnerable API endpoint.

Description

Pi-hole before 6 allows unauthenticated admin/api.php?setTempUnit= calls to change the temperature units of the web dashboard. NOTE: the supplier reportedly does "not consider the bug a security issue" but the specific motivation for letting arbitrary persons change the value (Celsius, Fahrenheit, or Kelvin), seen by the device owner, is unclear.

Impact

The primary impact of CVE-2024-44069 is on the integrity of the Pi-hole web dashboard's displayed information. By allowing unauthenticated users to change the temperature unit setting, attackers can cause confusion or mistrust in the dashboard's data presentation. While this does not compromise confidential information or availability of the service, it represents an unauthorized modification of system settings. In environments where Pi-hole is used for network-wide DNS filtering and monitoring, such unauthorized changes could be a vector for social engineering or misdirection attacks. Additionally, this vulnerability highlights a potential security design flaw that might indicate other endpoints could be similarly exposed, increasing the risk of further exploitation. Organizations relying on Pi-hole for network security and monitoring should consider the risk of unauthorized configuration changes and the potential for attackers to leverage this as part of multi-stage attacks.

Summary

CVE-2024-44069 is a vulnerability affecting Pi-hole versions prior to 6, where the web dashboard's temperature unit setting can be changed by any unauthenticated user via the admin/api.php?setTempUnit= API call. Pi-hole is a popular network-level ad and tracker blocking application that provides a web interface for monitoring and configuration. The vulnerability stems from a lack of authentication enforcement on this specific API endpoint, allowing remote attackers to alter the temperature unit displayed on the dashboard (switching between Celsius, Fahrenheit, or Kelvin) without any credentials. Although the supplier does not consider this a security issue, the ability to modify dashboard settings arbitrarily represents a violation of integrity (CWE-862: Missing Authorization). The CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) indicates that the vulnerability is remotely exploitable over the network with low attack complexity, no privileges or user interaction required, and impacts integrity but not confidentiality or availability. No patches or mitigations have been published at the time of disclosure, and there are no known exploits in the wild. This vulnerability does not directly expose sensitive data or disrupt service but could be used as part of a broader attack chain or to undermine user trust in the dashboard's accuracy.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 06:32 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats