CVE-2023-5816

Code Explorer <= 1.4.5 - Authenticated (Admin+) External File Reading

2024-10-29 00:00
Dmitrii Ignatyev

Strategic Overview

Status
Patched in 1.4.6
Affected Plugin
Code Explorer
Affected Version
<= 1.4.5
CVSS
4.9Medium
Weakness type
CWE-73 · External Control of File Name or Path
CVE
CVE-2023-5816
View all Code Explorer vulnerabilities

At a glance

CVE-2023-5816 is a medium-severity External Control of File Name or Path vulnerability in the Code Explorer WordPress plugin, affecting versions <= 1.4.5. It carries a CVSS score of 4.9 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 1.4.6; sites on affected versions should update now. Disclosed October 2024, reported by Dmitrii Ignatyev.

Vulnerability Overview

The Code Explorer plugin for WordPress is vulnerable to arbitrary external file reading in all versions up to, and including, 1.4.5. This is due to the fact that the plugin does not restrict accessing files to those outside of the WordPress instance, though the intention of the plugin is to only access WordPress related files. This makes it possible for authenticated attackers, with administrator-level access, to read files outside of the WordPress instance.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-73: External Control of File Name or Path

The product allows user input to control or influence paths or file names that are used in filesystem operations.

Remediation

Update to version 1.4.6, or a newer patched version

How does WordSec protect against this?

An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Code Explorer 1.4.6 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C