CVE-2026-25105
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 injecting malicious input into parameters of the Modbus command tool in the debug 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 · moderate confidenceAn OS command injection vulnerability in XWEB Pro version 1.12.1 and prior allows authenticated attackers to execute arbitrary OS commands on the target system by injecting malicious input into parameters of the Modbus command tool accessed through the debug route, leading to complete system compromise.
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 if XWEB Pro is accessibleCheck if the Copeland Xweb web interface is reachable on the target system (typically HTTP/HTTPS on common ports 80, 443, 8080). Look for XWEB Pro login pages or error messages that indicate the product.Affected if The XWEB Pro web application is exposed and accessible on the network.
-
Determine the firmware versionLog into the XWEB Pro administrative interface and navigate to the system information, about, or firmware version page. Alternatively, check HTTP response headers or error pages for version indicators.Affected if The installed firmware version is 1.12.1 or prior for any of the Xweb 300d Pro, Xweb 500d Pro, or Xweb 500b Pro models.
-
Verify if debug route is enabledAttempt to access common debug endpoints such as /debug, /admin/debug, /diagnostics/debug, or similar paths that may expose debug functionality. Check the web application for debug or diagnostic features.Affected if The debug route is accessible without being explicitly disabled or restricted.
-
Confirm Modbus command tool is availableAfter accessing the debug route, check if a Modbus command tool or Modbus configuration feature is present. Look for Modbus-related parameters or functionality in the debug interface.Affected if The Modbus command tool feature is enabled and accessible through the debug interface.
-
Check authentication statusDetermine if the debug route and Modbus tool require authentication. Note that the CVE states authenticated attackers can exploit this, so any valid administrative credentials would suffice.Affected if An attacker can obtain valid credentials to access the debug route with the Modbus command tool.
A user is affected if they are running XWEB Pro firmware version 1.12.1 or prior with the debug route accessible and the Modbus command tool enabled, allowing authenticated attackers to inject OS commands through Modbus parameters.
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.
From vendor dataUpgrade to a patched version of XWEB Pro. Until a patch is available, disable or restrict access to the debug route to trusted administrators only and implement strict input validation/sanitization on all Modbus command parameters to prevent command injection.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25105 — 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-25105 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