dbcve.org
File ManagerWordPress extension · Bitapps

CVE-2022-47599

HIGH · 7.2 CVSS v3.1 Published 2023-12-20
Fix available
A fix is available. Upgrade to 6.0.0 or later.
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
Deserialization of Untrusted Data vulnerability in File Manager by Bit Form Team File Manager – 100% Free & Open Source File Manager Plugin for WordPress | Bit File Manager.This issue affects File Manager – 100% Free & Open Source File Manager Plugin for WordPress | Bit File Manager: from n/a through 5.2.7.

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 · moderate confidence

This is an insecure deserialization vulnerability in the Bit File Manager WordPress plugin. Deserialization of untrusted data occurs when an application deserializes data from untrusted sources without proper validation, potentially allowing attackers to manipulate serialized objects to execute arbitrary code or cause denial of service. With a CVSS score of 7.2 (HIGH), this vulnerability poses significant risk to WordPress sites running the affected plugin versions up to 5.2.7.

MitigationUpdate the Bit File Manager plugin to the latest patched version once released, or remove the plugin if no patch is available. If immediate patching is not possible, restrict access to the plugin's administrative interfaces and monitor for suspicious activity.

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
File ManagerWordPress extension
Affected:< 6.0.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
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. Identify if Bit File Manager plugin is installed
    Check the WordPress plugins directory for the 'file-manager' or 'bit-file-manager' folder, typically located at /wp-content/plugins/. Alternatively, log into WordPress admin and navigate to Plugins > Installed Plugins and look for 'Bit File Manager' or 'Bitapps File Manager'.
    Affected if The plugin appears in the installed plugins list
  2. Locate the plugin version number
    In WordPress admin, find the plugin in the Installed Plugins list and look for the version number displayed beneath the plugin name. Alternatively, open the main plugin file (usually bit-file-manager.php or file-manager.php in the plugin directory) and search for a 'Version:' comment in the file header.
    Affected if A version number is displayed or found in the plugin file header
  3. Compare installed version against the vulnerable range
    The affected version range is any version before 6.0.0. Compare your installed version number to this threshold. For example, versions like 5.2.7, 5.2.6, 5.1.0, or any 5.x.x release are all affected.
    Affected if The installed version is less than 6.0.0 (for example, 5.2.7, 5.2.5, etc.)

A WordPress site is affected if the Bit File Manager (or Bitapps File Manager) plugin is installed and the installed version is any version lower than 6.0.0.

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 6.0.0 or later
Fixed in 6.0.0
Interim mitigation

Update the Bit File Manager plugin to the latest patched version once released, or remove the plugin if no patch is available. If immediate patching is not possible, restrict access to the plugin's administrative interfaces and monitor for suspicious activity.

Recommended fix Moderate confidence

6.0.0

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'File Manager' in the plugin list
  4. Click 'Update now' if an update to 6.0.0 is available, or manually upload version 6.0.0 of the plugin
  5. Verify the update completed successfully
  6. Test file management functionality to confirm the plugin works correctly after the update

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

Fix this in File Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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