dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-13914

HIGH · 7.2 CVSS v3.1 Published 2025-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 File Manager Advanced Shortcode plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.5.4 (file-manager-advanced-shortcode) and 2.5.6 (advanced-file-manager-pro-premium), via the 'file_manager_advanced' shortcode. This makes it possible for authenticated attackers, with Administrator-level access and above, to include and execute arbitrary JavaScript files on the server. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included. Sites currently using 2.5.4 (file-manager-advanced-shortcode) should be updated to 2.6.0 (advanced-file-manager-pro-premium).

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 File Manager Advanced Shortcode plugin for WordPress is vulnerable to Local File Inclusion (LFI) via the 'file_manager_advanced' shortcode. Authenticated attackers with Administrator-level access can include and execute arbitrary JavaScript files on the server by manipulating file path parameters in the shortcode, potentially achieving code execution.

MitigationUpdate the plugin to version 2.6.0 (advanced-file-manager-pro-premium) or later to remediate this vulnerability. Until then, restrict Administrator-level access and monitor for suspicious shortcode usage.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and look for 'File Manager Advanced Shortcode' or 'advanced-file-manager-pro-premium'. Note the version number displayed.
    Affected if The plugin is installed and the version shown is below 2.6.0 (or version cannot be determined).
  2. Check for shortcode usage in content
    Search WordPress database for posts/pages containing '[file_manager_advanced' shortcode: Run SQL query 'SELECT ID, post_title, post_type FROM wp_posts WHERE post_content LIKE "%[file_manager_advanced%"' in phpMyAdmin or via WP-CLI 'wp post list --post_type=any --search="file_manager_advanced"'.
    Affected if The shortcode is present in any published content.
  3. Inspect shortcode attributes for path parameters
    Examine the shortcode entries found. Look for attributes that might specify file paths, such as 'file', 'path', 'filename', or similar parameters that could be manipulated for LFI.
    Affected if Shortcode contains file path parameters or the shortcode is present with any attributes.
  4. Review recent administrator activity
    Check WordPress activity logs or server access logs for requests to pages containing the shortcode, particularly from administrator accounts. Look for unusual or repeated shortcode insertions.
    Affected if Shortcode has been recently added or modified by any administrator account.

You are affected if the File Manager Advanced Shortcode plugin is installed with a version below 2.6.0 and the shortcode is present in any content, especially with file path 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

Update the plugin to version 2.6.0 (advanced-file-manager-pro-premium) or later to remediate this vulnerability. Until then, restrict Administrator-level access and monitor for suspicious shortcode usage.

Recommended fix High confidence

File Manager Advanced Shortcode or Advanced File Manager Pro Premium version 2.6.0

  1. Log in to the WordPress admin dashboard with Administrator-level access
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'File Manager Advanced Shortcode' (free version) or 'Advanced File Manager Pro Premium' (premium version)
  4. Check the current installed version to confirm it is 2.5.4 (free) or 2.5.6 (premium) or lower
  5. Click 'Update Now' if an update to version 2.6.0 is available, or manually upload version 2.6.0 of the plugin
  6. After updating, verify the plugin version shows 2.6.0

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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