CVE-2021-26629
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 · uneditedA path traversal vulnerability in XPLATFORM's runtime archive function could lead to arbitrary file creation. When the .xzip archive file is decompressed, an arbitrary file can be d in the parent path by using the path traversal pattern ‘..\’.
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 confidenceA path traversal vulnerability exists in XPLATFORM's runtime archive function during decompression of .xzip archive files. By embedding path traversal sequences ('..\') in archive entries, an attacker can write arbitrary files to parent directories outside the intended extraction path, potentially achieving code execution or overwriting system files.
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< 9.2.2.284CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Check if Tobesoft XPLATFORM is installedLocate XPLATFORM runtime components on the system - look for XPLATFORM executables, DLLs, or runtime installation directories. Check for files named nexacro, xplatform, or related runtime libraries.Affected if XPLATFORM runtime software is present on the system
-
Determine the installed XPLATFORM versionLocate version information for the XPLATFORM runtime - this is typically found in the runtime DLLs, executable properties, or an installed version file. Compare the discovered version number against 9.2.2.284.Affected if Installed version is lower than 9.2.2.284
-
Identify .xzip archive usageSearch for .xzip files on the system or within application data directories. Review application logs or configuration to determine if the application processes or decompresses .xzip archives.Affected if The system processes or decompresses .xzip archive files
-
Check extraction path configurationReview application or XPLATFORM configuration files that define the extraction path for .xzip archives. Look for settings that control where archive contents are decompressed.Affected if Extraction path is not restricted to a safe, sandboxed directory
-
Verify file write permissions outside intended directoriesIf .xzip processing is active, review file system audit logs or application behavior to detect if files were written to parent directories outside the intended extraction path using '..\' path traversal sequences.Affected if Unrestricted write permissions allow files to be written outside the designated extraction directory
The environment is affected if Tobesoft XPLATFORM version is below 9.2.2.284 AND the system processes .xzip archive files with write access to locations that could be traversed via path manipulation.
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 · scoped9.2.2.284
Apply vendor-provided patches or updates to XPLATFORM runtime when available; validate and restrict .xzip file sources; consider implementing file system ACLs or sandboxing around the decompression functionality until a fix is deployed.
9.2.2.284 or later
- Identify all systems running XPLATFORM versions below 9.2.2.284
- Backup all current XPLATFORM configurations and data
- Test the upgrade to version 9.2.2.284 or later in a non-production environment
- Deploy the upgrade to production systems running XPLATFORM
- Verify the upgrade was successful by checking the version number
- Validate that the path traversal vulnerability is remediated by testing .xzip archive decompression
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26629 — 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-2021-26629 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