Strategic Overview
- Status
- Patched in 1.8.2
- Affected Plugin
- AdSanity
- Affected Version
< 1.8.2- CVSS
- 8.8High
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2022-4949
At a glance
CVE-2022-4949 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the AdSanity WordPress plugin, affecting versions < 1.8.2. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account. The issue is fixed in version 1.8.2; sites on affected versions should update now. Disclosed January 2022, reported by Jerome Bruandet.
Vulnerability Overview
The AdSanity plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'ajax_upload' function in versions up to, and including, 1.8.1. This makes it possible for authenticated attackers with Contributor+ level privileges to upload arbitrary files on the affected sites server which makes remote code execution possible.
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-434: Unrestricted Upload of File with Dangerous Type
AdSanity < 1.8.2 carries this weakness at ajax_upload, and reaching it takes any authenticated account. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.
If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For AdSanity the fix is 1.8.2: builds < 1.8.2 are affected, anything from 1.8.2 onward is not.
Remediation
Update to version 1.8.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to AdSanity: 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: AdSanity 1.8.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C