highCVE-2026-13347

Hide My WP Lite <= 1.3 - Unauthenticated Path Traversal to Arbitrary File Read via 'he_wrapper_js' Parameter

Q: What is affected by CVE-2026-13347?

Hide My WP Lite versions listed as affected should be reviewed: *-1.3.

Q: What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

Q: How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

Q: How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.

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.

ProductHide My WP Lite

CVSS7.5

EPSS0.00512

UpdatedJuly 13, 2026

Quick answer

Hide My WP Lite should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

*-1.3

Fixed versions

Apply the latest vendor-supported patched version.

How to fix it

Hide My WP Lite is affected by CVE-2026-13347, a information disclosure issue in versions up to 1.3. Wordfence lists the official remediation as updating to the latest vendor-supported patched release, or a newer patched version. Prioritize internet-facing WordPress sites, sites with public registration, customer portals, and admin workflows where the vulnerable feature is enabled. If immediate patching is not possible, disable the affected plugin or vulnerable feature, restrict access, and monitor for exploitation until the update is installed.

Inventory every WordPress site that has Hide My WP Lite installed, including staging, multisite, client, and WooCommerce environments.
Confirm the installed Hide My WP Lite version and compare it with the affected range from the Wordfence advisory.
Update Hide My WP Lite to the latest vendor-supported patched release, or to a newer vendor-supported patched version from the official WordPress update channel.
If the update cannot be applied immediately, disable Hide My WP Lite or the affected feature and restrict access with roles, authentication, WAF rules, or temporary route blocking.
Review plugin data, recent administrative actions, logs, and affected workflows for suspicious changes or abuse attempts.
Rotate administrator sessions, API keys, webhook secrets, and integration tokens if logs or content review suggest compromise.
Clear WordPress, object, CDN, page-builder, and browser caches after patching so vulnerable assets or stored payloads are not served.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

Confirm the running Hide My WP Lite version is the latest vendor-supported patched release or newer, and record the patched version in the remediation ticket.
Verify the vulnerable workflow no longer reproduces after the update or mitigation.
Review web server, WordPress, security plugin, WAF, and application logs for exploitation attempts before and after the fix.
Retest normal user, admin, checkout, form, API, or integration workflows to confirm the update did not break expected behavior.
Run a fresh Fixnx scan and document the public exposure state, patched version, log review, and any cleanup evidence.

Related categories

WordPress Path Traversal Arbitrary File Write

Trusted references

Wordfence advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Wordfence advisoryWordfence, NVD

FAQ

What is affected by CVE-2026-13347?

Hide My WP Lite versions listed as affected should be reviewed: *-1.3.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.