dbcve.org
Xweb 300d Pro FirmwareOperating system · Copeland

CVE-2026-20910

HIGH · 8.8 CVSS v3.1 Published 2026-02-27
Fix available
A fix is available. Upgrade to after 1.12.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
An OS command injection vulnerability exists in XWEB Pro version 1.12.1 and prior, enabling an authenticated attacker to achieve remote code execution on the system by injecting malicious input into the devices field of the firmware update action to achieve remote code execution.

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

OS command injection vulnerability in XWEB Pro <= 1.12.1 allows authenticated attackers to achieve remote code execution by injecting malicious commands into the 'devices' field during the firmware update action. The vulnerable parameter is not properly sanitized before being passed to system shell execution.

MitigationImplement strict input validation and sanitization on the devices parameter, preferably using allowlists and avoiding shell command construction; consider implementing role-based access controls to limit firmware update capabilities to necessary personnel only.

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
Xweb 300d Pro FirmwareOperating system
Affected:<= 1.12.1
Xweb 500d Pro FirmwareOperating system
Affected:<= 1.12.1
Xweb 500b Pro FirmwareOperating system
Affected:<= 1.12.1

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 the installed XWEB Pro version
    Access the device web interface and navigate to System Info, About, or Settings page to view the firmware version. Alternatively, check via API endpoint or CLI if available.
    Affected if The displayed firmware version is 1.12.1 or lower (for any of the models: Xweb 300d Pro, Xweb 500d Pro, or Xweb 500b Pro)
  2. Confirm the specific XWEB model
    Locate the model identifier in the web interface header, system information page, or device labeling. The affected models are Xweb 300d Pro, Xweb 500d Pro, and Xweb 500b Pro.
    Affected if The device is a Copeland Xweb 300d Pro, Xweb 500d Pro, or Xweb 500b Pro running firmware version 1.12.1 or lower
  3. Verify firmware update functionality is accessible
    Check if the firmware update or device configuration menu is accessible in the web interface. Look for a 'Firmware Update', 'Update Firmware', or similar option in the administrative panel.
    Affected if The firmware update feature exists and is accessible (regardless of whether you have privileges to use it)
  4. Inspect web server logs for firmware update requests
    Review access logs or audit logs for POST requests to firmware update endpoints, specifically looking for the 'devices' parameter in the request body.
    Affected if Log entries show firmware update requests containing unsanitized input in the devices parameter

You are affected if your Copeland Xweb device is running firmware version 1.12.1 or lower AND the firmware update feature with the devices parameter is present in your environment.

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.12.1
Interim mitigation

Implement strict input validation and sanitization on the devices parameter, preferably using allowlists and avoiding shell command construction; consider implementing role-based access controls to limit firmware update capabilities to necessary personnel only.

Recommended fix Moderate confidence

Any firmware version newer than 1.12.1 (contact vendor for specific fixed release number)

  1. 1. Identify the current firmware version of the affected Xweb device (300d Pro, 500d Pro, or 500b Pro)
  2. 2. Navigate to the vendor's official firmware download page or support portal
  3. 3. Download the latest available firmware version for your specific Xweb model
  4. 4. Before applying the update, backup current device configuration if the option is available
  5. 5. Upload and apply the new firmware through the device's web management interface
  6. 6. After reboot, verify the device is operational and confirm the new firmware version is installed
  7. 7. Test that the firmware update functionality no longer accepts injectable OS commands in the devices field
Caveat Review vendor release notes for any configuration or feature changes between versions

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

Fix this in Xweb 300d Pro Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-20910 — 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-20910 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