dbcve.org
Gs 5008pl FirmwareOperating system · Edimax

CVE-2026-32840

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-17
Fix available
A fix is available. Upgrade to after 1.00.54 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Edimax GS-5008PL firmware version 1.00.54 and prior contain a stored cross-site scripting vulnerability in the system_name_set.cgi script that allows attackers to inject arbitrary script code by manipulating the sysName parameter. Attackers can send a crafted POST request with malicious script payload that executes when management pages including system_data.js are viewed by administrators.

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 confidence

Stored cross-site scripting vulnerability in Edimax GS-5008PL firmware (version 1.00.54 and prior) allows attackers to inject arbitrary JavaScript via the sysName parameter in the system_name_set.cgi script. The malicious payload persists and executes when administrators view management pages that include system_data.js.

MitigationApply vendor firmware update if available; otherwise implement server-side input validation and output encoding on the sysName parameter to neutralize script injection.

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
Gs 5008pl FirmwareOperating system
Affected:<= 1.00.54

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model and firmware version
    Access the Edimax GS-5008PL web management interface and check the firmware version in System > Firmware Upgrade or System Information page. Alternatively, check via SNMP or console using 'show version' or similar command.
    Affected if Firmware version is 1.00.54 or lower
  2. Locate the system_name_set.cgi script
    Check if the web management interface responds to /cgi-bin/system_name_set.cgi or similar path. This is the endpoint that processes the sysName parameter.
    Affected if The CGI script is accessible and accepts sysName parameter without authentication bypass checks
  3. Inspect system_data.js for unsanitized output
    Access the management page that includes system_data.js (typically under System > General or System Information). View the page source and search for the sysName value being inserted into JavaScript context without proper encoding.
    Affected if The sysName value appears in the HTML/JavaScript response without HTML entity encoding (e.g., &lt;script&gt; appears as literal text rather than being encoded)
  4. Verify stored XSS persistence
    Submit a test payload via the sysName parameter in system_name_set.cgi (such as a benign alert or image tag). Then navigate away and return to any management page that loads system_data.js to see if the payload executes or renders.
    Affected if The injected payload persists and renders/executes when viewing management pages

You are affected if the Edimax GS-5008PL is running firmware version 1.00.54 or prior and the management interface displays the sysName value without encoding in system_data.js-loaded pages.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 1.00.54
Interim mitigation

Apply vendor firmware update if available; otherwise implement server-side input validation and output encoding on the sysName parameter to neutralize script injection.

Recommended fix Moderate confidence

Latest firmware version available on Edimax website (newer than 1.00.54)

  1. 1. Visit the official Edimax support website at www.edimax.com to check for available firmware updates.
  2. 2. Locate the GS-5008PL product page and navigate to the Downloads/Support section.
  3. 3. Download the latest available firmware version for the GS-5008PL switch.
  4. 4. Access the device web management interface and navigate to the firmware upgrade section.
  5. 5. Upload and apply the new firmware following the on-screen instructions.
  6. 6. After the upgrade completes, verify the system_name_set.cgi functionality works correctly and confirm the sysName parameter is now properly sanitized.
  7. 7. Clear browser cache and test that previously stored XSS payloads in sysName no longer execute.
Caveat Review release notes for any changes to management interface or loss of configuration settings during upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gs 5008pl Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32840 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32840 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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