PDF File Browser <= 1.3 - Remote Code Execution
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- PDF File Browser
- Affected Version
<= 1.3- CVSS
- 8.8High
- Weakness type
- CWE-94 · Improper Control of Generation of Code ('Code Injection')
- CVE
CVE pending
At a glance
This record tracks a high-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the PDF File Browser WordPress plugin, affecting versions <= 1.3. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). No fixed release has been reported yet; treat installations running this software as exposed. Disclosed October 2020, reported by Sammy Forgit.
Vulnerability Overview
The PDF File Browser plugin for WordPress is vulnerable to Remote Code Execution in versions up to, and including, 1.3 via the qqfile parameter. This allows authenticated attackers to execute code on the server.
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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-94: Improper Control of Generation of Code ('Code Injection')
Reaching this weakness in PDF File Browser <= 1.3 takes a caller who can reach the endpoint. 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. No fixed build of this plugin is recorded for PDF File Browser yet, so installs running <= 1.3 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
The attempt arrives as an ordinary request to PDF File Browser: 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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Scanner
- Alerts
External References
Related records
Other vulnerabilities in PDF File Browser
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C