CVE-2024-7627 json
Bit File Manager 6.0 - 6.5.5 - Unauthenticated Remote Code Execution via Race Condition
published 2y ago modified 4mo ago also EUVD-2024-48516
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.8%
- EPSS 2.8% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- bitapps file_manager 6.5.6
- giribaz file_manager 6.5.6
- wpjos library_file_manager 6.5.6
Is CVE-2024-7627 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
2.80% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- bitpressadmin Bit File Manager – 100% Free & Open Source File Manager and Code Editor for WordPress
- bitapps file_manager
Classification
- Weakness
- Technology feeds
References
-
plugins.trac.wordpress.org
/changeset/3138710/
patch
-
wordfence.com
/threat-intel/vulnerabilities/id/5f29de7a-3f15-4b6d-aad7-6a08151e2113?source=cve
third-party-advisory
-
plugins.trac.wordpress.org
/browser/file-manager/trunk/backend/app/Providers/FileEditValidator.php#L39
product
-
plugins.trac.wordpress.org
/browser/file-manager/trunk/backend/app/Providers/FileEditValidator.php#L88
product
Sources
- CVE List CVE-2024-7627
- NVD CVE-2024-7627
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.