dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-11010

HIGH · 7.2 CVSS v3.1 Published 2024-12-07
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 FileOrganizer – Manage WordPress and Website Files plugin for WordPress is vulnerable to Local JavaScript File Inclusion in all versions up to, and including, 1.1.4 via the 'default_lang' parameter. This makes it possible for authenticated attackers, with Administrator-level access and above, to include and execute arbitrary JavaScript files on the server, allowing the execution of any JavaScript code in those files. 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.

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 FileOrganizer WordPress plugin versions up to 1.1.4 contain a Local JavaScript File Inclusion vulnerability via the 'default_lang' parameter. Authenticated administrators can supply a path to an arbitrary JavaScript file which the plugin will include and execute server-side, allowing arbitrary JS code execution and potential privilege escalation.

MitigationUpgrade to version 1.1.5 or later which contains the patch. Until then, restrict administrator-level access to trusted users only and consider disabling the plugin if unused.

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 FileOrganizer plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'FileOrganizer' in the list. Note the version number displayed under the plugin name.
    Affected if The plugin appears in the installed plugins list with a version number of 1.1.4 or lower
  2. Check the installed plugin version
    If the plugin is installed, locate the version string in the plugin header comment by viewing the main plugin file (usually wp-content/plugins/file-organizer/file-organizer.php or similar) via FTP or file manager.
    Affected if The version read from the file header is 1.1.4 or any version lower than 1.1.4
  3. Confirm administrator accounts exist
    In WordPress admin, navigate to Users > All Users and review the list of users with Administrator role. Alternatively, query the wp_users and wp_usermeta database tables for users with wp_capabilities containing 'administrator'.
    Affected if There is at least one user account with Administrator role, providing the authentication level needed to exploit this vulnerability
  4. Verify the default_lang parameter is processed
    Inspect the plugin PHP source code for handling of the 'default_lang' parameter, typically in AJAX handlers or admin_init hooks. Search for code that includes or requires files based on this parameter without proper validation.
    Affected if The plugin code contains logic that includes JavaScript files based on the 'default_lang' parameter without sanitizing the path, allowing arbitrary file inclusion

If FileOrganizer plugin is installed with version 1.1.4 or lower and the site has at least one Administrator-level user, the environment is affected by this vulnerability.

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 version 1.1.5 or later which contains the patch. Until then, restrict administrator-level access to trusted users only and consider disabling the plugin if unused.

Recommended fix High confidence

FileOrganizer version 1.1.5 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate FileOrganizer – Manage WordPress and Website Files
  4. Click 'Update Now' if an update is available, or manually download the latest version from wordpress.org/plugins/file-organizer/ and upload via Plugins > Add New > Upload Plugin
  5. Verify the updated version is 1.1.5 or later
  6. Test that the plugin functionality works correctly after update

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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