dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-11585

HIGH · 7.5 CVSS v3.1 Published 2024-12-06
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

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 WP Hide & Security Enhancer plugin for WordPress is vulnerable to arbitrary file contents deletion due to a missing authorization and insufficient file path validation in the file-process.php in all versions up to, and including, 2.5.1. This makes it possible for unauthenticated attackers to delete the contents of arbitrary files on the server, which can break the site or lead to data loss.

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 WP Hide & Security Enhancer plugin for WordPress contains an unauthenticated arbitrary file deletion vulnerability in file-process.php. The issue stems from missing authorization checks combined with insufficient file path validation, allowing any unauthenticated attacker to delete the contents of arbitrary files on the server by manipulating file paths in requests to the vulnerable component.

MitigationUpdate the WP Hide & Security Enhancer plugin to version 2.5.2 or later. If immediate patching is not possible, consider deploying a WAF rule to block suspicious file deletion requests to the file-process.php endpoint.

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 WP Hide & Security Enhancer plugin is installed
    Check the WordPress plugins directory for the wp-hide-security-enhancer folder, or list active plugins via wp-cli: wp plugin list --status=active --field=name
    Affected if The plugin folder wp-hide-security-enhancer exists in /wp-content/plugins/ or appears in the active plugins list
  2. Check the installed plugin version
    If the plugin is active, access /wp-admin/plugins.php and look at the version column for 'WP Hide & Security Enhancer', or inspect the main plugin file header in wp-content/plugins/wp-hide-security-enhancer/ for the Version: field
    Affected if The version number is lower than 2.5.2 (e.g., 2.5.1, 2.5.0, or earlier)
  3. Confirm file-process.php exists and is accessible
    Check for the presence of file-process.php in the plugin directory: ls -la /wp-content/plugins/wp-hide-security-enhancer/admin/include/file-process.php or attempt a HEAD request to the URL if the plugin exposes it publicly
    Affected if The file file-process.php exists in the plugin's admin/include/ directory and responds to requests
  4. Review access logs for suspicious file deletion attempts
    Check web server access logs (Apache error.log, Nginx access.log, or WAF logs) for POST or GET requests to the file-process.php endpoint containing file path parameters, especially requests with patterns like 'action=delete' or path traversal sequences (e.g., ../../)
    Affected if Unauthenticated requests to file-process.php with file path parameters appear in logs, particularly with delete-related action parameters

You are affected if the WP Hide & Security Enhancer plugin is installed with a version lower than 2.5.2 and the file-process.php component is accessible, enabling unauthenticated arbitrary file deletion.

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

Update the WP Hide & Security Enhancer plugin to version 2.5.2 or later. If immediate patching is not possible, consider deploying a WAF rule to block suspicious file deletion requests to the file-process.php endpoint.

Recommended fix Moderate confidence

Plugin version 2.5.2 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate WP Hide & Security Enhancer
  4. Check the current version (should be 2.5.1 or earlier)
  5. Update the plugin to the latest available version (2.5.2 or later)
  6. Verify the update was successful and the site remains functional

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11585 — 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-2024-11585 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