LiveActive security incident?Get immediate response
CVE Record

CVE-2022-47599: WordPress File Manager Plugin <= 5.2.7 is vulnerable to PHP Object Injection

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.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE affects the Bit File Manager WordPress plugin through version 5.2.7. A high-privileged user could trigger unsafe PHP object deserialization, potentially causing limited data exposure, data change, or disruption. It is not listed in CISA KEV, and the provided sources do not show active exploitation.

Executive priority

Treat this as a moderate-priority WordPress plugin issue. It is not evidenced as actively exploited, but affected sites should be remediated during the next normal security maintenance window, sooner for externally managed or high-value WordPress environments.

Technical view

CVE-2022-47599 is CWE-502 deserialization of untrusted data in File Manager by Bit Form Team, package file-manager, through 5.2.7. CVSS 3.1 is 5.5 with network attack vector, high complexity, high privileges required, no user interaction, changed scope, and low CIA impact.

Likely exposure

Exposure is limited to WordPress sites running File Manager – 100% Free & Open Source File Manager Plugin for WordPress | Bit File Manager through 5.2.7. Risk is higher where many administrators exist or admin accounts are weakly governed.

Exploitation context

The source bundle supports a vulnerable condition but does not provide exploit evidence. KEV is false. The CVSS vector indicates exploitation requires high privileges and high complexity, which reduces broad internet-scale urgency but still matters for compromised-admin scenarios.

Researcher notes

Evidence is limited to CVE metadata and Patchstack’s vulnerability entry. Do not assume unauthenticated exploitation or a specific patched version from the provided bundle. Focus validation on plugin presence, version, administrator exposure, and vendor-confirmed remediation state.

Mitigation direction

  • Inventory WordPress sites for the Bit File Manager plugin and version.
  • Update or remove affected plugin installations according to vendor or Patchstack guidance.
  • Restrict administrator access to trusted users only.
  • Enforce MFA and strong credential hygiene for WordPress administrators.
  • Monitor WordPress and server logs for unusual privileged plugin activity.

Validation and detection

  • Confirm whether each WordPress site runs file-manager version 5.2.7 or earlier.
  • Verify the plugin is updated, disabled, or removed after remediation.
  • Review administrator accounts for unnecessary privileges or suspicious additions.
  • Check vendor or Patchstack records for a named fixed version.
  • Document affected sites, remediation status, and residual exceptions.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-47599 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:L1.33.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2022-47599Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
File Manager by Bit Form TeamFile Manager – 100% Free & Open Source File Manager Plugin for WordPress | Bit File Managerfile-manager, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.