CVE Tools

CVE-2026-1001

Domoticz < 2026.1 Stored XSS via Hardware Configuration Endpoint

No known exploitation. EPSS puts it in the 8th percentile. No fix published yet.

Published Updated Sources: CVE.org, NVD

What to do

No fixed build or workaround is published yet. Limit exposure and watch for a patch.

Steps

Written by AI from the record
  1. Check your Domoticz version in the web interface (or by viewing the system/version info) and determine whether it is older than 2026.1.
  2. If you are on a Domoticz version prior to 2026.1, plan an upgrade immediately to Domoticz 2026.1 or later.
  3. Review who has administrative access to the Domoticz web interface, and remove/limit admin privileges to only trusted staff.
  4. After upgrading, monitor Domoticz logs and your browser/client behavior for unexpected prompts, strange page behavior, or new/changed hardware/device names containing unusual characters.

What it is

From the CVE record

Domoticz versions prior to 2026.1 contain a stored cross-site scripting vulnerability in the Add Hardware and rename device functionality of the web interface that allows authenticated administrators to execute arbitrary scripts by supplying crafted names containing script or HTML markup. Attackers can inject malicious code that is stored and rendered without proper output encoding, causing script execution in the browsers of users viewing the affected page and enabling unauthorized actions within their session context.

In plain language

Written by AI from the record

CVE-2026-1001 is a Domoticz web bug that lets an administrator save malicious scripts in device/hardware names; it then runs when other people view the affected page—so you should update if you use Domoticz and have any admin accounts.

In Domoticz, CVE-2026-1001 is a stored cross-site scripting (CWE-79) flaw in the hardware configuration/rename workflow where a high-privilege web administrator can inject crafted hardware/device names containing script/HTML that is later rendered to other users without proper output encoding, enabling script execution in their browsers.

If you're affected

  • Browser takeover in your admin sessions
  • Unauthorized actions as logged-in users
  • Exposure of local/session information
  • Operational disruption from malicious UI changes

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS8th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.2% chance of exploitation activity in the next 30 days, which ranks it in the 8th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

6 events over 111 days, from the signal feeds we watch.

  1. Record updated
  2. OpenVAS check added
  3. Record updated
  4. Publishedweakness classified, att&ck mapped

Affected products

And 1 more affected product. See all after sign-in

Technical detail

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

Scored 4.8 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required HighRequires admin or elevated privileges
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality LowSome restricted information is disclosed, but limited in scope
  • Integrity LowData modification is possible but limited in scope or consequence
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Domoticz, not every advisory.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store