CVE-2022-31792
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA stored cross-site scripting (XSS) vulnerability exists in the management web interface of WatchGuard Firebox and XTM appliances. A remote attacker can potentially execute arbitrary JavaScript code in the management web interface by sending crafted requests to exposed management ports. This is fixed in Fireware OS 12.8.1, 12.5.10, and 12.1.4.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA stored cross-site scripting (XSS) vulnerability exists in the management web interface of WatchGuard Firebox and XTM security appliances. A remote attacker can inject malicious JavaScript code through crafted requests to exposed management ports, which then executes when administrators access the affected interface pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 12.0.0, < 12.1.4>= 12.2.0, < 12.5.10= 12.6.1= 12.6.3= 12.6.4= 12.7.0= 12.7.1= 12.7.2= 12.8.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the Fireware OS versionLog into the Firebox management web interface and navigate to System Status or Dashboard. Alternatively, access the CLI and use the 'firewareOS' or 'system' command to retrieve the firmware version.Affected if The installed version falls within any of these ranges: >= 12.0.0 and < 12.1.4; >= 12.2.0 and < 12.5.10; or equals 12.6.1, 12.6.3, 12.6.4, 12.7.0, 12.7.1, 12.7.2, or 12.8.0
-
Confirm management web interface is accessibleVerify that the Firebox management web interface ports (default HTTPS ports 443 or 8080) are listening and reachable from network perspectives. Check device network configuration for exposed management interfaces.Affected if The management web interface is exposed to network segments that include untrusted users or the internet
-
Verify if remote management is enabledIn the Firebox management interface, go to Network > Interfaces and review the interface settings. Check whether 'HTTPS' or 'Web UI' management is enabled on external or non-internal interfaces.Affected if Management web interface is enabled on any interface that is accessible from untrusted networks
-
Review management interface logs for suspicious requestsAccess the Firebox logs through the Web UI (Log > View Logs) or exported log files. Search for unusual or unexpected HTTP/HTTPS requests to management ports that may indicate injection attempts.Affected if Unusual request patterns or evidence of injection attempts targeting management interfaces exists in the logs
A user is affected if the Fireware OS version matches the affected version ranges AND the management web interface is exposed to potentially untrusted network access.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped12.1.412.5.10
Apply the appropriate firmware update (Fireware OS 12.8.1, 12.5.10, or 12.1.4) after verifying current version and ensuring proper backup/configuration export. If immediate patching is not possible, restrict access to management interfaces to trusted IP addresses only.
Upgrade to Fireware OS 12.8.1 (or at minimum 12.5.10 or 12.1.4 depending on your current branch)
- 1. Identify the current Fireware OS version running on the WatchGuard Firebox or XTM appliance
- 2. If running version >= 12.0.0 and < 12.1.4, plan upgrade to Fireware OS 12.1.4 or later (preferably 12.5.10 or 12.8.1)
- 3. If running version >= 12.2.0 and < 12.5.10, plan upgrade to Fireware OS 12.5.10 or later (preferably 12.8.1)
- 4. If running version 12.6.1 or 12.6.3, plan upgrade to Fireware OS 12.8.1
- 5. Before upgrading, review WatchGuard release notes for any migration or compatibility considerations
- 6. Download the appropriate Fireware OS firmware from the WatchGuard support portal
- 7. Apply the firmware upgrade following WatchGuard's standard upgrade procedures
- 8. After upgrade, verify the management web interface is accessible and functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31792 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-31792 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data