dbcve.org
Xweb 500b Pro FirmwareOperating system · Copeland

CVE-2026-25111

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 requests sent to the restore route.

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

XWEB Pro versions 1.12.1 and prior contain an OS command injection vulnerability in the restore functionality. An authenticated attacker can inject malicious operating system commands through input fields in restore route requests, achieving remote code execution on the underlying system.

MitigationUpgrade to a version newer than 1.12.1 that addresses this vulnerability; if an update is unavailable, disable or restrict access to the restore functionality and implement strict input validation/sanitization on all user-supplied parameters before they reach system command execution functions.

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 500b Pro FirmwareOperating system
Affected:<= 1.12.1
Xweb 300d Pro FirmwareOperating system
Affected:<= 1.12.1
Xweb 500d 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 XWEB Pro product variant
    Access the device web interface and locate the system information or about page. Look for the specific model designation (Xweb 500b Pro, Xweb 300d Pro, or Xweb 500d Pro) displayed in the interface header, footer, or status/summary page.
    Affected if The product is any of the three listed variants (500b Pro, 300d Pro, or 500d Pro)
  2. Check the installed firmware version
    In the device web interface, navigate to the system information, status, or firmware version page. Record the exact firmware version number displayed.
    Affected if The firmware version is 1.12.1 or any version lower than 1.12.1
  3. Verify if restore functionality is accessible
    Attempt to access the restore feature endpoint in the web interface. This is typically found under a restore, backup/restore, system restore, or configuration restore menu item. Check if the route loads or responds.
    Affected if The restore functionality is present and accessible in the web interface
  4. Confirm authentication is required for restore
    Try to access the restore functionality without logging in, or verify in the authentication settings that the restore feature requires valid user credentials.
    Affected if Authentication is not enforced or uses weak/default credentials, making unauthorized restore access possible

A user is affected if they are running any of the three XWEB Pro variants with firmware version 1.12.1 or lower and the restore functionality is accessible (with or without proper authentication).

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

Upgrade to a version newer than 1.12.1 that addresses this vulnerability; if an update is unavailable, disable or restrict access to the restore functionality and implement strict input validation/sanitization on all user-supplied parameters before they reach system command execution functions.

Recommended fix Moderate confidence

Contact vendor for fixed firmware version (likely > 1.12.1)

  1. 1. Identify the specific Xweb Pro model (500b, 300d, or 500d) currently deployed in the environment
  2. 2. Check the current firmware version installed on the device
  3. 3. Contact the device vendor (Copeland) to obtain the firmware version that addresses CVE-2026-25111
  4. 4. Download the updated firmware from an official vendor source
  5. 5. Review vendor release notes for any special upgrade instructions or prerequisites
  6. 6. Back up current device configuration before initiating firmware update
  7. 7. Apply the firmware update via the device's management interface
  8. 8. Verify the update was successful and the device is operational
Caveat Firmware updates may temporarily disrupt device operation; ensure maintenance window is scheduled

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

Fix this in Xweb 500b Pro Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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