Is Code Explorer safe to use?

Laskyr does not give safety verdicts. Code Explorer is closed on wordpress.org. Closed on 2026-01-29 (reason given: Security Issue). Closed plugins get no updates through WordPress, so new security holes will not be fixed for you. Keep Code Explorer on the latest version and remove it if you do not use it.

Which versions of Code Explorer are vulnerable?

Known issues on record (newest first): Path traversal / file read (1.4.6 and older); Security issue (1.4.5 and older). The full list with sources is on this page.

What should I do if my Code Explorer is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update code-explorer). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · code-explorer · data as of 2026-11-04

Is Code Explorer safe? Known vulnerabilities and latest version

Status: Closed 2026-01-29
Known issues on record: 2
Unpatched in latest: 0

What to do

Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.

With WP-CLI, once you have a replacement: wp plugin deactivate code-explorer && wp plugin delete code-explorer

Check your version

Known vulnerabilities

2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 2 record(s) do not state which versions are affected.

medium 4.9 CVE-2025-15487 · published 2026-02-04

Path traversal / file read in Code Explorer (1.4.6 and older)

Affected: 1.4.6 and older
Fixed in: unknown
Access needed (per CVSS): Needs an admin-level account
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Code Explorer plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 1.4.6 via the 'file' parameter. This makes it possible for authenticated attackers, with Administrator-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.

NVD CVE-2025-15487 Wordfence advisory Plugin source

medium 4.9 CVE-2023-5816 · published 2024-10-30

Security issue in Code Explorer (1.4.5 and older)

Affected: 1.4.5 and older
Fixed in: unknown
Access needed (per CVSS): Needs an admin-level account
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

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.

NVD CVE-2023-5816 Wordfence advisory Code change (fix)wordpress.org

Recent activity

2026-01-29 — closed on wordpress.org (Security Issue).
2026-02-04 — Path traversal / file read disclosed (CVE-2025-15487), fix version not stated.
2024-10-30 — Security issue disclosed (CVE-2023-5816), fix version not stated.

Free. We check the CVE feeds every day and email you only when a new issue for Code Explorer (code-explorer) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Path traversal and file read (1)

Where this data comes from

Version, last update, installs, closure: wordpress.org/plugins/code-explorer (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/code-explorer"><img src="https://laskyr.com/plugins/code-explorer/badge.svg" alt="Code Explorer vulnerability status"></a>

← Check another plugin · Free hacked-site scan