CVE-2023-31928
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 reflected cross-site scripting (XSS) vulnerability exists in Brocade Webtools PortSetting.html of Brocade Fabric OS version before Brocade Fabric OS v9.2.0 that could allow a remote unauthenticated attacker to execute arbitrary JavaScript code in a target user’s session with the Brocade Webtools application.
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 reflected cross-site scripting (XSS) vulnerability in the PortSetting.html page of Brocade Webtools allows remote unauthenticated attackers to inject arbitrary JavaScript code through unsanitized user input, which executes in the context of a victim's browser session.
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< 9.2.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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check Fabric OS versionLog into the Fabric OS device via CLI and execute 'version' or 'firmwareshow' to display the installed OS versionAffected if The displayed version number is below 9.2.0 (e.g., 9.1.x, 9.0.x, 8.x, etc.)
-
Verify Webtools is enabledAccess the device CLI and run 'webtools -status' or check if port 443 or 80 is listening for HTTP/HTTPS connections to the Webtools interfaceAffected if Webtools service is running and accepting connections
-
Confirm PortSetting.html is accessibleAttempt to access https://<device-ip>/webtools/PortSetting.html (or HTTP) from a permitted network location - the page loads without authentication redirectAffected if The PortSetting.html page loads and accepts user input parameters in the URL without sanitization
-
Assess network exposureReview firewall rules, ACLs, or network segmentation to determine if Webtools interface is reachable from untrusted networksAffected if Webtools is accessible from networks outside the trusted administrative zone
You are affected if your Fabric OS version is below 9.2.0 AND the Webtools PortSetting.html page is accessible (with or without authentication) on your network.
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 · scoped9.2.0
Upgrade Brocade Fabric OS to v9.2.0 or later to obtain the patch. Until then, restrict access to Webtools interface via network segmentation or firewall rules, and consider deploying WAF rules to detect and block XSS payloads.
Brocade Fabric OS v9.2.0
- Upgrade Brocade Fabric OS to version 9.2.0 or later to remediate this vulnerability.
- Verify the upgrade by checking the Fabric OS version using the 'version' command or through Webtools.
- After upgrade, confirm that the PortSetting.html page in Webtools no longer reflects unsanitized input.
- Test that the Webtools application functions normally after the upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31928 — 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-2023-31928 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