dbcve.org
WpideWordPress extension · Xplodedthemes

CVE-2024-9546

MEDIUM · 5.3 CVSS v3.1 Published 2024-10-15
Fix available
A fix is available. Upgrade to 3.5.0 or later.
See remediation →
62/100
Remediation priority · Elevated
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 WPIDE – File Manager & Code Editor plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 3.4.9. This is due to the plugin utilizing the PHP-Parser library, which outputs parser rebuild command execution results. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website.

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 WPIDE plugin for WordPress uses the PHP-Parser library which outputs parser rebuild command execution results, inadvertently exposing the full server file system path to unauthenticated attackers. This information disclosure is network-exploitable without authentication and reveals the web application's absolute path.

MitigationUpdate the WPIDE plugin to version 3.4.10 or later. If an updated version is unavailable, disable the plugin until a patched release is provided.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WpideWordPress extension
Affected:< 3.5.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 WPIDE plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'WPIDE' or 'Xplodedthemes Wpide' in the plugin list
    Affected if WPIDE plugin appears in the installed plugins list
  2. Check installed WPIDE version
    In the Plugins list, locate WPIDE and note the version number displayed under the plugin name, or check the plugin's main PHP file header for the Version constant
    Affected if The installed version is lower than 3.5.0 (for example: 3.4.9, 3.4.8, etc.)
  3. Verify PHP-Parser endpoint is accessible
    Send an HTTP GET request to the WPIDE plugin's parser rebuild endpoint (typically /wp-content/plugins/wpide/vendor/nikic/php-parser/lib/ or similar PHP-Parser related endpoint)
    Affected if The endpoint responds and contains server file system paths in the output
  4. Confirm path disclosure vulnerability
    Inspect the HTTP response from the PHP-Parser endpoint for absolute server paths (such as /var/www/ or C:\inetpub\)
    Affected if The response exposes the full server file system path

You are affected if WPIDE plugin version lower than 3.5.0 is installed and the PHP-Parser endpoint is accessible, resulting in absolute path disclosure

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
Upgrade available Upgrade to 3.5.0 or later
Fixed in 3.5.0
Interim mitigation

Update the WPIDE plugin to version 3.4.10 or later. If an updated version is unavailable, disable the plugin until a patched release is provided.

Recommended fix High confidence

3.5.0

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate WPIDE – File Manager & Code Editor
  4. If an update is available, click 'Update Now' to update to version 3.5.0
  5. Alternatively, download version 3.5.0 from the WordPress plugin repository
  6. Deactivate and delete the existing plugin, then upload and activate the new version
  7. Verify the plugin is running version 3.5.0 or later

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

Fix this in Wpide Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA0.5 h
3.5 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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