# CVE-2023-5816: Code Explorer <= 1.4.5 - Authenticated (Admin+) External File Reading

> Authenticated administrators can read arbitrary files outside the WordPress instance due to insufficient path restrictions in the Code Explorer plugin.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Oct 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-g463-pw3x-jmj3

## What is CVE-2023-5816?

CVE-2023-5816 is a medium-severity path traversal vulnerability in qriouslad Code Explorer, published on 30 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2023-5816?

It affects 1 product.


Products: Bowo Code Explorer.

## How do I fix CVE-2023-5816?

No fix has been published for CVE-2023-5816 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-5816 being exploited?

There is no known exploitation of CVE-2023-5816 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-5816 and fix it if it is affected.

What it is: CVE-2023-5816 is a medium-severity path traversal vulnerability in qriouslad Code Explorer, published on 30 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-5816 in the wild and no public exploit code.

Affected product: qriouslad Code Explorer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-5816/ (Markdown: https://insights.sbomify.com/CVE-2023-5816/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-5816
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-5816
- OSV: https://osv.dev/vulnerability/CVE-2023-5816

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-5816/
Summaries are generated and may contain mistakes; the official description above is the record.