dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-13347

HIGH · 7.5 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Hide My WP Lite plugin for WordPress (versions up to 1.3) contains an arbitrary file read vulnerability in the elementor_assets_filter() function. The function accepts he_wrapper_js or he_wrapper_css query parameters and directly concatenates this user input onto ABSPATH before passing it to file_get_contents() without any path traversal validation, allow-listing, or extension checking. Although output passes through wp_kses_post(), this only filters HTML and does not prevent disclosure of arbitrary file contents. Exploitation requires the Elementor plugin and 'Hide Elementor' feature to be enabled.

MitigationUpgrade to a patched version of Hide My WP Lite that addresses the path traversal vulnerability, or disable the 'Hide Elementor' feature if the plugin cannot be updated immediately.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Hide My WP Lite plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for the hide-my-wp folder, or list installed plugins via wp-cli: wp plugin list --name='hide-my-wp'
    Affected if The plugin folder exists in the WordPress installation
  2. Determine installed version of Hide My WP Lite
    Read the plugin's main PHP file header comment (typically hide-my-wp.php in wp-content/plugins/hide-my-wp/) to find the Version: field, or query via WP-CLI: wp plugin get hide-my-wp --field=version
    Affected if The version is 1.3 or lower (any version up to and including 1.3 is affected)
  3. Verify Elementor plugin is installed
    Check for the elementor folder in wp-content/plugins/, or query via WP-CLI: wp plugin list --name='elementor'
    Affected if Elementor plugin is present in the WordPress installation
  4. Confirm Hide Elementor feature is enabled
    Check WordPress options table (wp_options) for option_name containing 'hide_elementor' or 'hmwp_elementor', or inspect the plugin settings file for the enabled state of the Hide Elementor feature
    Affected if The Hide Elementor feature setting is turned ON or enabled in the plugin configuration

All four conditions must be true for the environment to be affected: Hide My WP Lite version 1.3 or lower is installed, Elementor plugin is present, and the Hide Elementor feature is enabled, allowing the arbitrary file read via he_wrapper_js or he_wrapper_css parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of Hide My WP Lite that addresses the path traversal vulnerability, or disable the 'Hide Elementor' feature if the plugin cannot be updated immediately.

Recommended fix Moderate confidence

Latest version of Hide My WP Lite (verify in WordPress plugin repository; version 1.4 or higher may contain the fix)

  1. 1. Check if the Hide My WP Lite plugin is actively used on the WordPress site; if not, deactivate and remove it to eliminate the vulnerability.
  2. 2. Verify whether the Elementor page builder plugin is installed; this vulnerability requires Elementor to be present.
  3. 3. If Elementor is installed, check whether the 'Hide Elementor' feature within Hide My WP Lite is enabled; the vulnerability only exploits when this feature is active.
  4. 4. If the plugin is needed, attempt to upgrade Hide My WP Lite to the latest available version from the WordPress plugin repository.
  5. 5. Alternatively, disable the 'Hide Elementor' feature in Hide My WP Lite settings as a temporary mitigation if upgrading is not immediately possible.
  6. 6. After upgrading or disabling the feature, verify the fix by confirming he_wrapper_js and he_wrapper_css parameters no longer return arbitrary file contents.
  7. 7. Consider using a WAF rule to block path traversal patterns (e.g., ../../) in query parameters as an additional layer of protection.
Caveat Upgrading Hide My WP Lite may change functionality or configuration settings; test in a staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13347 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13347 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data