CVE-2025-25625
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 vulnerability exists in FS model S3150-8T2F switches running firmware s3150-8t2f-switch-fsos-220d_118101 and web firmware v2.2.2, which allows an authenticated web interface user to bypass input filtering on user names, and stores un-sanitized HTML and Javascript on the device. Pages which then present the user name without encoding special characters will then cause the injected code to be parsed by the browsers of other users accessing the web interface.
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 vulnerability in FS S3150-8T2F switches (firmware s3150-8t2f-switch-fsos-220d_118101, web firmware v2.2.2) allows authenticated users to bypass input filtering on username fields, storing unsanitized HTML/JavaScript that executes in other users' browsers when viewing the username.
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= 2.2.2= s3150-8t2f-switch-fsos-220d_118101CVSS 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 switch firmware versionLog into the switch CLI and run 'show version' or 'show system-info' to confirm the firmware build is s3150-8t2f-switch-fsos-220d_118101Affected if Firmware version matches s3150-8t2f-switch-fsos-220d_118101 or web firmware is v2.2.2
-
Verify web interface is enabledCheck if the HTTP/HTTPS web management interface is active via 'show web' or 'show http' CLI command, or by attempting to access the switch IP in a browser on port 80 or 443Affected if Web interface is enabled and accessible
-
Confirm authentication accessDetermine if you have valid administrator credentials to access the web management interface or CLIAffected if You have authenticated access to the switch management
-
Test username field for XSS injectionIn the web interface, navigate to user account settings and attempt to set a username containing HTML/JavaScript payload such as <script>alert('XSS')</script>, then save the configurationAffected if The username field accepts and stores unsanitized HTML/JavaScript without encoding or rejection
-
Verify XSS executes in another sessionLog out, then log in as a different user or clear your browser session and view the page where usernames are displayed (such as user list, login page error messages, or admin panel)Affected if The injected JavaScript executes when viewing the username in another browser session
You are affected if your switch runs firmware s3150-8t2f-switch-fsos-220d_118101 (or web firmware v2.2.2), the web interface is enabled, and the username field accepts and stores unsanitized HTML/JavaScript that executes in other users' browsers.
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.
From vendor dataUpdate to patched firmware version when available and/or implement output encoding on all user-provided data displayed in the web interface.
- Consultation4.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,440.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-25625 — 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-2025-25625 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