CVE-2021-26618
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 improper input validation leading to arbitrary file creation was discovered in ToWord of ToOffice. Remote attackers use this vulnerability to execute arbitrary file included malicious code.
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 confidenceImproper input validation in the ToWord component of ToOffice allows remote attackers to create arbitrary files with malicious content on the target system, leading to remote code execution.
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< 3.15.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify ToOffice is installedCheck for ToOffice installation by searching program directories or using system inventory tools for 'Tmax ToOffice' or 'ToOffice' softwareAffected if ToOffice software is found on the system
-
Determine installed ToOffice versionUse system software inventory, check program files, or run: version detection command for installed ToOffice software (e.g., via registry, installed programs list, or 'tooffice -v' if available)Affected if Installed version is lower than 3.15.6 (any version shown as 3.15.5, 3.14.x, or earlier)
-
Confirm ToWord component presenceCheck for ToWord module/component within the ToOffice installation directory or verify ToWord executable existsAffected if ToWord component or executable is present within the ToOffice installation folder
-
Inspect for unauthorized file creationReview user-accessible directories (Downloads, Documents, Desktop, temp folders) for newly created files with suspicious extensions (especially executable or script files) that were not intentionally created by the userAffected if Unexpected files with malicious content appear in accessible directories after using ToOffice to open documents
User is affected if Tmax ToOffice version lower than 3.15.6 is installed with the ToWord component present and operational.
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 · scoped3.15.6
Apply available vendor patches for ToOffice immediately. Until patches are applied, restrict network exposure and avoid opening untrusted documents with ToOffice.
ToOffice 3.15.6
- Identify the current installed version of ToOffice on the system
- Verify the installed version is less than 3.15.6
- Back up all important data and documents before proceeding with the upgrade
- Download ToOffice version 3.15.6 or later from the official vendor source
- Install the updated version following the vendor's standard installation procedure
- Verify the installation completed successfully and confirm the version is 3.15.6 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26618 — 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-26618 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