dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-8743

MEDIUM · 6.8 CVSS v3.1 Published 2024-10-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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 Bit File Manager – 100% Free & Open Source File Manager and Code Editor for WordPress plugin for WordPress is vulnerable to Limited JavaScript File Upload in all versions up to, and including, 6.5.7. This is due to a lack of proper checks on allowed file types. This makes it possible for authenticated attackers, with Subscriber-level access and above, and granted permissions by an administrator, to upload .css and .js files, which could lead to Stored Cross-Site Scripting.

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 Bit File Manager WordPress plugin fails to properly validate file types during upload, allowing authenticated users with Subscriber-level access (when granted permissions by an administrator) to upload .js and .css files. These files are stored on the server and can be executed in users' browsers, leading to Stored Cross-Site Scripting.

MitigationAdministrators should immediately revoke file upload permissions from untrusted users. The vendor should implement server-side validation using MIME type verification and file signature (magic byte) checks, not just file extension validation.

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

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/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 Bit File Manager plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Bit File Manager' or check the file /wp-content/plugins/file-manager/ or similar directory. Note the installed version.
    Affected if The plugin is installed and active
  2. Check if untrusted users have upload permissions
    Navigate to File Manager > Settings > Permissions. Look for roles with 'create' or 'upload' capabilities. Specifically check if Subscriber role or any role assigned to untrusted users has file upload/create permissions enabled.
    Affected if Subscriber-level or untrusted users have been granted file upload or file creation permissions through the plugin settings
  3. Verify allowed file extensions include .js or .css
    In File Manager settings, examine the configuration for allowed file extensions. Look for entries in file upload/extension whitelist that include .js or .css.
    Affected if The plugin configuration allows .js or .css file extensions to be uploaded

A user is affected if Bit File Manager plugin is installed AND Subscriber-level or untrusted users have been granted upload permissions AND the plugin allows .js or .css file uploads, enabling stored XSS.

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

Administrators should immediately revoke file upload permissions from untrusted users. The vendor should implement server-side validation using MIME type verification and file signature (magic byte) checks, not just file extension validation.

Recommended fix Moderate confidence

Bit File Manager version 6.5.8 or latest available release

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Bit File Manager' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/bit-file-manager/ and upload it manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the new version number reflects the security patch (version 6.5.8 or later)

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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