CVE-2026-78616: Dimension Stored XSS via Trusted CA Certificate Configuration
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record loaded 2026-09-20.
What to do now held facts and links
- Upgrade to 2.3.1 or later CVE record
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
A Stored Cross-Site Scripting (XSS) vulnerability in WatchGuard Dimension's Trusted CA certificate configuration allows an authenticated administrator to execute arbitrary JavaScript in another authenticated administrator's web browser by saving a carefully crafted certificate.
- weakness
- CWE-79
- affected
- WatchGuard Dimension
- versions
- WatchGuard Dimension < 2.3.1
- fixed in
- 2.3.1
- severity
- 4.8 CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
- assigned by
- WatchGuard
- published
- 2026-08-27
check us psirt.watchguard.com
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 28 Aug 2026 | 0.00164 | |
| 2 Sep 2026 | 0.00186 | |
| 28 Sep 2026 | 0.00303 |
3 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.00 on 2026-09-28 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: 2.3.1 (CVE record, loaded 2026-09-20). A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2026-78616', '2026-10-03T23:59:59.999999Z', now());Identity above is quoted from the CVE Program record, corpus cvelistv5_20260920, recorded 30 Sep 2026.