CVE-2026-27517
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 · uneditedBinardat 10G08-0800GSM network switch firmware version V300SP10260209 and prior reflect unsanitized user input in the web interface, allowing an attacker to inject and execute arbitrary JavaScript in the context of an authenticated user.
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 confidenceThe Binardat 10G08-0800GSM network switch firmware V300SP10260209 and prior contains a reflected cross-site scripting (XSS) vulnerability in its web interface. User-supplied input is reflected back to the browser without proper sanitization or output encoding, allowing an authenticated attacker to inject and execute arbitrary JavaScript in the context of other authenticated users.
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<= V300SP10260209CVSS 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.
-
Identify Binardat 10G08-0800GSM device in environmentLocate network devices matching this model designation through network scans, asset inventory, or physical inspection of device labels. Note the device management IP address if found.Affected if The device is a Binardat 10G08-0800GSM network switch.
-
Determine installed firmware versionAccess the device management interface (web UI or CLI) and navigate to system information, firmware version, or about page. Compare the displayed version to V300SP10260209.Affected if Firmware version is V300SP10260209 or any version number that sorts lower (e.g., V300SP10260208, earlier releases).
-
Verify web interface is enabledCheck device configuration for HTTP/HTTPS web management service status. Attempt to reach the device IP on common web ports (80, 443, 8080) to confirm the interface is accessible.Affected if The web-based management interface is enabled and reachable on the network.
-
Confirm authenticated access is possibleVerify that valid administrative credentials exist or can be obtained for the device, as the XSS requires an authenticated session to exploit.Affected if You have or can obtain administrative credentials to log into the device web interface.
You are affected if you have a Binardat 10G08-0800GSM switch running firmware version V300SP10260209 or earlier, with the web interface enabled and accessible using valid admin credentials.
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 dataApply available firmware patches from the vendor that address input validation and output encoding in the web interface. Until a patch is available, consider deploying a web application firewall or restricting administrative access to trusted networks to reduce exposure.
- Consultation4.0 h
- Implementation12.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 $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27517 — 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-2026-27517 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