CVE-2026-23702
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 · uneditedAn 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 sending malicious input injected into the server username field of the import preconfiguration action in the API V1 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 confidenceOS command injection vulnerability in XWEB Pro version 1.12.1 and prior. An authenticated attacker can achieve remote code execution by injecting malicious commands through the server username field in the import preconfiguration action of the API V1 route.
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<= 1.12.1<= 1.12.1<= 1.12.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify XWEB Pro product variant and versionAccess the web interface or check system information to determine if the device runs Xweb 300d Pro, Xweb 500d Pro, or Xweb 500b Pro firmware, and note the exact firmware version number installedAffected if The installed firmware version is 1.12.1 or any earlier version (1.12.0, 1.11.x, etc.) on any of the three affected product models
-
Confirm API V1 route is accessibleVerify the web application's API V1 endpoint is reachable (typically at /api/v1/ or similar path based on the product's web interface structure)Affected if The API V1 route responds and is not disabled or restricted by network-level controls
-
Check if import preconfiguration feature existsLocate the import preconfiguration action within the API V1 interface - this is typically a function that allows loading saved configuration filesAffected if The import preconfiguration functionality is present and accessible in the API V1 route
-
Verify authentication is required for the vulnerable endpointDetermine whether the import preconfiguration action requires valid authentication credentials to accessAffected if The endpoint accepts authenticated requests - note that if authentication is disabled or uses weak defaults, the attacker may already meet the authentication requirement for exploitation
Your environment is affected if you are running any of the three Copeland XWEB Pro models (300d, 500d, or 500b) with firmware version 1.12.1 or prior, and the API V1 import preconfiguration feature is accessible to authenticated users.
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.
dbcve · scopedImplement strict input validation and sanitization on all user-supplied fields, particularly the server username parameter. Replace direct system command execution with parameterized APIs or safe libraries. Apply vendor patch if available.
Xweb 300d/500d/500b Pro Firmware > 1.12.1 (latest available from vendor)
- Identify the exact Xweb device model (300d Pro, 500d Pro, or 500b Pro) currently deployed
- Access the device administration interface or console
- Navigate to the firmware update section
- Check the manufacturer's official support website (webapps.copeland.com or related Copeland/Xweb support channels) for the latest firmware version
- Download the firmware version newer than 1.12.1
- Follow the manufacturer's documented firmware upgrade procedure to apply the update
- After upgrading, verify the firmware version shows a version number greater than 1.12.1
- If available, apply any subsequent security patches released after the initial fix
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23702 — 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-23702 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