CVE-2023-40498 is a critical flaw in LG Simple Editor 3.21.0: the cp command (in makeDetailContent) has a directory traversal bug that leads to remote code execution. NVD scores it 9.8 (Critical). LG told the Zero Day Initiative it will not fix it, so no patch exists. Restrict access to the application or remove it.
What's affected
The record lists one product and one version: LG Simple Editor 3.21.0 (the CPE vendor field reads lg). The weakness class is CWE-22.
The vulnerable code is the cp command (in makeDetailContent), which does not validate a user-supplied path before using it in file operations, and the advisory says an unauthenticated remote attacker can use that to execute code. Code execution as SYSTEM means full control of the host, so the record scores confidentiality, integrity and availability all as high.
No fixed version exists. The Zero Day Initiative advisory ZDI-23-1204 (tracked as ZDI-CAN-19925) says ZDI reported the issue to LG on 14 February 2023. On 8 August 2023 the vendor stated it does not plan to fix it now or in the future. ZDI then published it as a zero day advisory on 24 August 2023. NVD added the record on 3 May 2024. The record does not say whether versions other than 3.21.0 are affected, and the advisory names no safe version.
It is not in CISA's Known Exploited Vulnerabilities catalog, and the advisory does not say it is exploited in the wild.
How to check if you're exposed
There is no package feed to scan for this one, so exposure comes down to whether the application is installed and reachable. The record lists no authentication requirement, so network reachability is the only barrier.
On a Windows host, check whether LG Simple Editor is installed and which version:
Get-Package | Where-Object Name -like "*Simple Editor*"
Also look in Apps and features, because not every installer registers with that command. Then list listening sockets and match the owning process to the application:
netstat -ano | findstr LISTENING
tasklist /FI "PID eq 1234"
Replace 1234 with a process ID from the first command. If you find version 3.21.0 and the service answers from any network other than a trusted administration segment, treat the host as exposed. Add the host to your software inventory either way, so a later fix notice from LG reaches someone who can act on it.
What to do now
- Inventory every host that has LG Simple Editor installed and record the version.
- Remove network access you do not need. Block inbound connections to the service at the host firewall and the perimeter, and allow only named administrators.
- If the product is not in active use, uninstall it. With no vendor fix, retirement is the only complete remedy.
- Watch for new files or processes appearing under the application's directories and for child processes started by the application's service account.
- Ask LG whether a patched version or a replacement exists, and recheck the Zero Day Initiative advisory for updates.
Why it matters
Directory traversal is a path validation failure. The program takes a path from the request and uses it for a file operation without confirming it stays inside the folder it was meant to use. When the operation can write or copy files, the same mistake can place content where the system will later run it, which is how a file bug becomes a code execution bug.
The advisory does not describe how the code execution is reached beyond the missing path check, and this post does not guess. What matters for defenders is the combination of no authentication, a network attack vector and SYSTEM context. The vendor has said it will not patch this, which is the main reason the guidance here is about reducing exposure.
This is one of many records filed against LG Simple Editor 3.21.0 from the same ZDI batch, each tied to a different method. Each bug stands alone, so the safest reading is that the product as a whole should stay off untrusted networks.
Quick check
Does an attacker need an account to reach this?
No. The record and the Zero Day Initiative advisory both say authentication is not required, and the vector shows no privileges required.
Is a patch available for CVE-2023-40498?
No. According to the ZDI advisory, LG said on 8 August 2023 that it does not plan to fix the vulnerability. Check the advisory for later changes before you rely on that.
Sources
- Zero Day Initiative advisory ZDI-23-1204
- Safeguard Gold entry for CVE-2023-40498
- NVD record for CVE-2023-40498, as supplied in the Safeguard CVE dataset
Last reviewed: 19 October 2026.
