CVE-2024-7627

Bit File Manager 6.0 - 6.5.5 - Unauthenticated Remote Code Execution via Race Condition

2024-09-04 00:00
TANG Cheuk Hei (siunam)

Strategic Overview

Status
Patched in 6.5.6
Affected Plugin
File Manager
Affected Version
6.0 – 6.5.5
CVSS
8.1High
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE-2024-7627
View all File Manager vulnerabilities

At a glance

CVE-2024-7627 is a high-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the File Manager WordPress plugin, affecting versions 6.0 – 6.5.5. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 6.5.6; sites on affected versions should update now. Disclosed September 2024, reported by TANG Cheuk Hei (siunam).

Vulnerability Overview

The Bit File Manager plugin for WordPress is vulnerable to Remote Code Execution in versions 6.0 to 6.5.5 via the 'checkSyntax' function. This is due to writing a temporary file to a publicly accessible directory before performing file validation. This makes it possible for unauthenticated attackers to execute code on the server if an administrator has allowed Guest User read permissions.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-94: Improper Control of Generation of Code ('Code Injection')

File Manager 6.0 – 6.5.5 carries this weakness at checkSyntax, and reaching it takes no account at all. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.

The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For File Manager the fix is 6.5.6: builds 6.0 – 6.5.5 are affected, anything from 6.5.6 onward is not.

Remediation

Update to version 6.5.6, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: File Manager 6.5.6 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

https://www.cve.org/CVERecord?id=CVE-2024-7627https://www.wordfence.com/threat-intel/vulnerabilities/id/5f29de7a-3f15-4b6d-aad7-6a08151e2113https://nvd.nist.gov/vuln/detail/CVE-2024-7627

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C