CVE-2026-22877
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 arbitrary file-read vulnerability exists in XWEB Pro version 1.12.1 and prior, enabling unauthenticated attackers to read arbitrary files on the system, and potentially causing a denial-of-service attack.
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 confidenceXWEB Pro 1.12.1 and prior contains an unauthenticated arbitrary file-read vulnerability, likely due to insufficient input validation on file path parameters. Attackers can exploit this to read sensitive system files, potentially exposing credentials, configuration data, or other confidential information, while also potentially triggering denial-of-service conditions.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 Copeland XWEB Pro is runningCheck for running processes or services related to Xweb (xweb, XWEB300d, XWEB500d, XWEB500b) using task manager, ps, or service management tools. Also check if port 80/443 or custom ports are listening for XWEB web interface.Affected if The XWEB Pro web service is running and accessible on the network
-
Determine the installed firmware versionAccess the XWEB web interface (typically via HTTP/HTTPS on the device IP) and navigate to System Info, About, or Settings pages to view the firmware version. Alternatively, check the firmware file or system documentation if you have local access.Affected if The firmware version is 1.12.1 or any version prior to 1.12.1
-
Verify if remote unauthenticated access is enabledCheck the XWEB configuration settings for remote access, web access, or network access permissions. Confirm whether authentication is required for file-related endpoints.Affected if Remote unauthenticated access to the web interface is enabled without require_authentication set to true
-
Check for file access endpoints in the web applicationReview the XWEB web application's available routes, parameters, or API endpoints that handle file operations (download, view, export). Look for parameters that might accept file paths.Affected if The web application exposes endpoints that accept file path parameters without proper validation
A user is affected if Copeland XWEB Pro firmware version 1.12.1 or prior is running and the web interface is accessible remotely with unauthenticated access enabled, allowing path traversal attacks to read arbitrary files.
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 when available. If no patch exists, implement strict input validation and access controls on file-serving endpoints, and consider temporarily restricting network access to the affected service.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22877 — 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-22877 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