dbcve.org
Xweb 500b Pro FirmwareOperating system · Copeland

CVE-2026-24663

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-27
Fix available
A fix is available. Upgrade to after 1.12.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 unauthenticated attacker to achieve remote code execution on the system by sending a crafted request to the libraries installation route and injecting malicious input into the request body.

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 · moderate confidence

An OS command injection vulnerability in XWEB Pro versions 1.12.1 and prior allows unauthenticated attackers to achieve remote code execution by sending crafted requests with malicious input to the libraries installation route.

MitigationImmediate action required: update to patched version if available; otherwise, disable the vulnerable libraries installation route, implement strict input validation, and apply web application firewall rules to block malicious payloads.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 firmware version
    Access the device admin interface or check system information page to locate the firmware version number for the Xweb Pro device
    Affected if Firmware version is 1.12.1 or lower on Xweb 500b Pro, Xweb 300d Pro, or Xweb 500d Pro models
  2. Verify the libraries installation route is exposed
    Attempt to access the libraries installation endpoint on the web interface (commonly at /libraries, /install_libraries, or similar path) without authentication
    Affected if The route is accessible without requiring authentication
  3. Confirm no input validation is applied
    Send a benign test request with special characters to the libraries installation endpoint and observe if the input is validated or sanitized before processing
    Affected if Special characters or command payloads are accepted and processed without filtering or rejection

Your environment is affected if you are running any of the three Xweb Pro models with firmware version 1.12.1 or lower and the libraries installation route is accessible without 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

Immediate action required: update to patched version if available; otherwise, disable the vulnerable libraries installation route, implement strict input validation, and apply web application firewall rules to block malicious payloads.

Recommended fix Moderate confidence

Firmware version newer than 1.12.1 (contact vendor for exact patched release)

  1. 1. Identify the current firmware version of the XWEB device (500b Pro, 300d Pro, or 500d Pro) by accessing the device administration interface.
  2. 2. Check the vendor's official support portal or firmware download page for the latest available firmware version.
  3. 3. Download the firmware version newer than 1.12.1 that includes the security patch for CVE-2026-24663.
  4. 4. Before upgrading, backup the current device configuration to ensure recovery is possible if issues arise.
  5. 5. Upload and install the new firmware version following the vendor's documented upgrade procedure.
  6. 6. After upgrading, verify the device is functioning correctly and the vulnerability is no longer present.
  7. 7. Confirm the new firmware version by checking the device administration interface.
Caveat Review vendor release notes for any configuration or feature changes between 1.12.1 and the target version

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

Fix this in Xweb 500b Pro Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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