Vulnerability · CVE-2017-14615
An FBX-5313 issue was discovered in WatchGuard Fireware before 12.0.
Published Sep 20, 2017 · catalog updated Jun 17, 2026 · An FBX-5313 issue was
Last checked Nov 7, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2017-14615. EPSS is 0.95%. Act only if a listed version of An FBX-5313 issue was is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (An FBX-5313 issue was).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-86134 · High
- CVE-2026-90441 · High
- CVE-2026-86136 · High
- CVE-2026-86133 · High
- CVE-2026-86132 · High
- Severity
- Medium6.1
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.95%
- Remediation
- Version ranges on file
- Affected products
- cpe watchguard/fireware
An FBX-5313 issue was discovered in WatchGuard Fireware before 12.0. When a failed login attempt is made to the login endpoint of the XML-RPC interface, if JavaScript code, properly encoded to be consumed by XML parsers, is embedded as value of the user element, the code will be rendered in the context of any logged in user in the Web UI visiting "Traffic Monitor" sections "Events" and "All." As a side effect, no further events will be visible in the Traffic Monitor until the device is restarted.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe watchguard/fireware<= 11.12.4
How to fix CVE-2017-14615
Upgrade
CVE-2017-14615 lists a fix boundary at 11.12.4. Compare the installed build with that boundary before you change production.
Version check
Affected <= 11.12.4
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2017-14615. EPSS is 0.95%. Act only if a listed version of An FBX-5313 issue was is installed.
Which versions are affected?
Compare what you have installed with <= 11.12.4. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-79: Cross-site Scripting (XSS). EPSS 0.95%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Sep 20, 2017 · Monitored products — high
Detected
An FBX-5313 issue was discovered in WatchGuard Fireware before 12.0. When a failed login attempt is made to the login endpoint of the XML-RPC interface, if JavaScript code, properly encoded to be consumed by XML parsers, is embedded as value of the user element, the code will be rendered in the context of any logged in user in the Web UI visiting "Traffic Monitor" sections "Events" and "All." As a
Jun 17, 2026 · Monitored products — high
Updated
An FBX-5313 issue was discovered in WatchGuard Fireware before 12.0. When a failed login attempt is made to the login endpoint of the XML-RPC interface, if JavaScript code, properly encoded to be consumed by XML parsers, is embedded as value of the user element, the code will be rendered in the context of any logged in user in the Web UI visiting "Traffic Monitor" sections "Events" and "All." As a
Sources
- CVE.orgVulnerability recordCVE-2017-14615
Official CVE identifier
cve.org - Monitored products — highVendor advisoryCVE-2017-14615
An FBX-5313 issue was discovered in WatchGuard Fireware before 12.0. When a failed login attempt is made to the login endpoint of the XML-RPC interface, if JavaScript code, properly encoded to be consumed by XML parsers, is embedded as value of the user element, the code will be rendered in the context of any logged in user in the Web UI visiting "Traffic Monitor" sections "Events" and "All." As a
nvd.nist.gov
References
Freshness
Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- CVE.orgNov 7, 2026
- Monitored products — highNov 6, 2026