Heatmiser Wifi Thermostat 1.7 networkSetup.htm credentials storage
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Heatmiser Wifi Thermostat 1.7. It has been rated as problematic. Affected by this issue is some unknown functionality of the file networkSetup.htm. Performing a manipulation results in credentials storage. This vulnerability is cataloged as CVE-2018-25396. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.
Details
A vulnerability was found in Heatmiser Wifi Thermostat 1.7. It has been classified as problematic. This affects an unknown function of the file networkSetup.htm. The manipulation with an unknown input leads to a credentials storage vulnerability. CWE is classifying the issue as CWE-256. Storing a password in plaintext may result in a system compromise. This is going to have an impact on confidentiality. The summary by CVE is:
Heatmiser Wifi Thermostat 1.7 contains a credential disclosure vulnerability that allows unauthenticated attackers to retrieve administrative credentials by accessing the networkSetup.htm page. Attackers can request the networkSetup.htm endpoint and extract plaintext username and password values from HTML form fields to gain administrative access to the thermostat.
The weakness was shared by d0wnp0ur as 45623. The advisory is shared at exploit-db.com. This vulnerability is uniquely identified as CVE-2018-25396 since 05/29/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1552 for this issue.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:networkSetup.htm it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Exploit-DB (45623). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.1
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Credentials storageCWE: CWE-256 / CWE-255
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Google Hack: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔒
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
05/29/2026 Advisory disclosed05/29/2026 CVE reserved
05/29/2026 VulDB entry created
05/29/2026 VulDB entry last update
Sources
Advisory: 45623Researcher: d0wnp0ur
Status: Not defined
CVE: CVE-2018-25396 (🔒)
GCVE (CVE): GCVE-0-2018-25396
GCVE (VulDB): GCVE-100-367269
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 05/29/2026 18:54Changes: 05/29/2026 18:54 (81)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.