Tmax ToOffice arbitrary file creation vulnerability

published 2022-02-18 4y ago modified 2026-06-17 4mo ago also EUVD-2021-13412

cvss: 7.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.0%; EPSS 1.0% chance of exploitation in 30 days, percentile 62%
public exploits: 0; none known

An 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.

Patch / fix

fixed in 1

tmax tooffice 3.15.6

Is CVE-2021-26618 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.00% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.1	CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.5	AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

TmaxSoft Co., Ltd ToOffice

Classification

Weakness

CWE-20 Improper Input Validation

References

krcert.or.kr /krcert/secNoticeView.do?bulletin_writing_sequence=36456
third-party-advisory, vdb-entry

Sources

CVE List CVE-2021-26618
NVD CVE-2021-26618

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.