Big File Uploads <= 2.1.2 - Authenticated (Author+) Full Path Disclosure
Strategic Overview
- Status
- Patched in 2.1.3
- Affected Plugin
- Big File Uploads – Increase Maximum File Upload Size
- Affected Version
<= 2.1.2- CVSS
- 4.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2024-8538
At a glance
CVE-2024-8538 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Big File Uploads WordPress plugin, affecting versions <= 2.1.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 2.1.3; sites on affected versions should update now. Disclosed September 2024, reported by 2tokui.
Vulnerability Overview
The Big File Uploads – Increase Maximum File Upload Size plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 2.1.2. This is due the plugin not sanitizing a file path in an error message. This makes it possible for authenticated attackers, with author-level access and above, to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in Big File Uploads <= 2.1.2 takes an account at Author level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Big File Uploads the fix is 2.1.3: builds <= 2.1.2 are affected, anything from 2.1.3 onward is not.
Remediation
Update to version 2.1.3, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: Big File Uploads 2.1.3 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Other vulnerabilities in Big File Uploads – Increase Maximum File Upload Size
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C