Plugins · hide-wp-login · data as of 2026-11-04
Is Hide My WP Lite safe? Known vulnerabilities and latest version
- Status
- Closed 2026-06-29
- Known issues on record
- 1
- 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 hide-wp-login && wp plugin delete hide-wp-login
Check your version
Known vulnerabilities
1 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. 1 record(s) do not state which versions are affected.
high 7.5 CVE-2026-13347 · published 2026-07-10
Path traversal / file read in Hide My WP Lite (1.3 and older)
- Affected
- 1.3 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Hide My WP Lite plugin for WordPress is vulnerable to Arbitrary File Read in versions up to and including 1.3 via the he_wrapper_js and he_wrapper_css query parameters processed by the elementor_assets_filter() function. This is due to the function concatenating user-supplied input directly onto ABSPATH and passing the result to file_get_contents() without any path traversal validation, allow-list, realpath containment, or extension check; the result is then echoed in the HTTP response. Although the output is passed through wp_kses_post(), that function only filters HTML tags and does not prevent disclosure of arbitrary file contents. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the affected site's server (such as wp-config). Note: The exploit requires the Elementor plugin and the 'Hide Elementor' feature to be enabled.
Recent activity
- 2026-06-29 — closed on wordpress.org (Security Issue).
- 2026-07-10 — Path traversal / file read disclosed (CVE-2026-13347), fix version not stated.
Get an email when Hide My WP Lite has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Hide My WP Lite (hide-wp-login) 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/hide-wp-login (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/hide-wp-login"><img src="https://laskyr.com/plugins/hide-wp-login/badge.svg" alt="Hide My WP Lite vulnerability status"></a>