WatchGuard Dimension reflected XSS in device configuration history page
- Exploited
- No known exploitation
- Fix
- Fixed in 2.3.2
- Who is exposed
- Not reported
Summary
A cross-site scripting flaw in WatchGuard Dimension's Device Configuration History page lets a remote attacker who has a low-privilege login with view permission on a device run JavaScript in another logged-in user's browser. The attacker must trick that user into opening a specially crafted link.
Written by a model
Original description
A reflected Cross-Site Scripting (XSS) vulnerability in WatchGuard Dimension's Device Configuration History page allows an authenticated attacker with view permission on a device to execute arbitrary JavaScript in another authenticated user's browser by enticing the victim to open a specially crafted link.
What to do
Upgrade to a fixed version: 2.3.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-81434 (Dimension Reflected XSS in Device Configuration History Page), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-81434 (entry last updated 2026-11-19):
Affected:
- WatchGuard Dimension: from 2.0, fixed in 2.3.2
Fixed versions: 2.3.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-81434 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-81434 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://psirt.watchguard.com/CVE-2026-81434
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-81434
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-81434"}.Affected versions
- WatchGuard DimensionFrom 2.0 · fixed in 2.3.2
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.8/10CVSS 4.8
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | psirt.watchguard.com · CVE-2026-81434 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-81434 |
| Record | NVD · CVE-2026-81434 |
Questions about CVE-2026-81434
Is CVE-2026-81434 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-81434?
Dimension: from 2.0 before 2.3.2.
Source: cve.now feed data
How do I fix CVE-2026-81434?
Upgrade to a fixed version: 2.3.2.
Source: cve.now feed data
Related
- CVE-2026-86130Dimension Improper Authentication in Log Collection Service Allows Unauthenticated Remote Code Execution
- CVE-2026-86094Dimension Session Hijack via Exposed Session Tokens in Diagnostic Logs
- CVE-2026-84322Dimension Session Hijack via Exposed Session Tokens in Management API
- CVE-2026-93912Dimension Code Injection in Log Notification Processing Allows Remote Code Execution
- CVE-2026-93911Dimension SQL Injection in Log Collector Allows Remote Code Execution
- CVE-2026-103580Dimension OS Command Injection in Package Update Allows Remote Code Execution as Root
No corrections so far. Something wrong on this page? Report an error.