On this page (7 sections)

iDocView has a critical flaw tracked as CVE-2023-54422. According to the NVD record, iDocView before 13.10.1_20231115 contains an unrestricted file upload weakness in the /html/2word endpoint that lets unauthenticated attackers write arbitrary files and achieve remote code execution.

If you run iDocView anywhere an untrusted party could reach it, treat this as urgent. The same description states that the Shadowserver Foundation first observed exploitation evidence on 2023-11-22, so this is not purely theoretical.

What happened

The NVD description says the /html/2word endpoint accepts a url parameter, and that a crafted GET request can make it download linked resources using an unsanitized path and an unblocked .jsp extension. No login is needed. The stated result is that attackers can write arbitrary files and achieve remote code execution.

The record was published on 2026-11-18, while the exploitation observation it cites dates from 2023-11-22 and the build name in the affected range carries a 20231115 date stamp. The research does not explain the gap between those dates, so we make no claim about why the entry appeared later or how widely the flaw was abused.

Coverage is thin. Besides the NVD entry, the references list a VulnCheck advisory, a Nuclei detection template and a secrss article. We could not read those pages, so details beyond the NVD description are unconfirmed here. The record also cites no vendor advisory.

Why this weakness is dangerous

Unrestricted file upload (CWE-434) means an application lets a user place a file on the server without enough checks on its name, type or location. The NVD description points to two missing controls in this case: the path of the downloaded resource is not sanitized, and the .jsp extension is not blocked.

As general background, not a documented detail of this product: remote code execution on any server usually means an attacker can run commands with the privileges of the affected service, which can expose data and secrets on that host and may give a foothold for further attacks. The NVD record does not describe what an attacker could reach on an iDocView host specifically.

Who is exposed

Based on the record, the exposed group is any iDocView instance running a build before 13.10.1_20231115 that an attacker can send requests to. Because the description says no authentication is required, reachability of the endpoint is what matters.

  • Instances older than 13.10.1_20231115, including ones you did not install yourself.
  • Instances where the /html/2word endpoint can be reached by someone you do not trust.

As a general assumption, not something the research states: components like this are sometimes set up by contractors or bundled into larger projects and then forgotten, so it is worth asking who deployed what. The research does not list product editions, deployment types or other build lines, so confirm your exact build rather than assuming a version family is safe.

How to check your exposure

Start by finding every iDocView instance you own. Then read the version from your installation, release notes or admin interface, and compare it with 13.10.1_20231115. Per the record, anything older is affected.

Next, look for signs that the endpoint has been used. This read-only search runs on the web server or reverse proxy host and lists log lines that mention the vulnerable path; adjust the log directories to your setup. Review any hit that did not come from your own testing.

Search access logs for requests to the /html/2word endpoint (read-only; run on the web server or…Shell
grep -R "/html/2word" /var/log/nginx/ /var/log/apache2/ 2>/dev/null

Also look for unexpected .jsp files in the application's directories, particularly ones with recent modification times that you cannot tie to a deployment. This read-only command lists .jsp files changed in the last 30 days under a directory you choose; replace the placeholder path with your iDocView install location.

List recently modified .jsp files under the iDocView directory (read-only; replace the path)Shell
find /path/to/idocview -name "*.jsp" -mtime -30 -ls
Caution. If you find an unexpected .jsp file or a suspicious request that returned a success status, assume the server may be compromised. Do not simply delete the file and move on; follow an incident process and rotate any secrets stored on that host.

What to do now

  1. Inventory every iDocView deployment and record its exact build number.
  2. Contact the vendor to confirm which release fixes CVE-2023-54422, since the record names no advisory, and upgrade to a build at or after 13.10.1_20231115.
  3. If you cannot upgrade immediately, remove the instance from public access or restrict it to trusted IP ranges, and consider blocking requests to /html/2word at your reverse proxy or firewall until it is patched.
  4. Search logs for requests to /html/2word and inspect the application directories for unexpected .jsp files.
  5. If anything suspicious turns up, isolate the host, preserve logs, rebuild from a known-good image and rotate credentials and API keys stored on it.
  6. Run the application service as a low-privilege account and avoid making its web directories writable by that service where possible.
  7. Consider placing a web application firewall or reverse proxy in front of the service so unexpected paths and parameters can be filtered.
Tip. Blocking a path at the proxy is a stopgap, not a fix. Plan the upgrade even if the block is in place.

Detection and monitoring afterwards

Keep watching for requests to the /html/2word endpoint from unfamiliar addresses, new executable files in web directories, and unexpected outbound connections from the iDocView host. Alert on file creation events under the application path.

From the outside, a security scan of your verified site can help you spot exposed services, and certificate, DNS and header monitoring helps you notice unplanned changes. These do not replace patching, and an outside view cannot confirm what is on your server's disk; see what outside-in malware detection can and cannot see. For a broader response plan, read what to do if your website is hacked.

Timeline

Dates stated in or implied by the NVD record
DateEvent
2023-11-15Date stamp in the build name 13.10.1_20231115 (the version before which iDocView is affected)
2023-11-22Shadowserver Foundation first observed exploitation evidence (per NVD)
2026-11-18CVE-2023-54422 published in NVD

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2023-54422: iDocView before 13.10.1_20231115 contains an unrestricted file upload vulnerability in the /html/2word endpoint that allows unauthenticated attackers to write…nvd.nist.gov ·
  • iDocView
  • CVE-2023-54422
  • file upload
  • remote code execution
  • CWE-434