WP SVG Icons <= 3.2.2 - Cross-Site Request Forgery to Remote Code Execution
Strategic Overview
- Status
- Patched in 3.2.3
- Affected Plugin
- WP SVG Icons
- Affected Version
< 3.2.3- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2019-14216
At a glance
CVE-2019-14216 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP SVG Icons WordPress plugin, affecting versions < 3.2.3. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.2.3; sites on affected versions should update now. Disclosed August 2019, reported by Zeroauth.
Vulnerability Overview
An issue was discovered in the svg-vector-icon-plugin (aka WP SVG Icons) plugin through 3.2.2 for WordPress. wp-admin/admin.php?page=wp-svg-icons-custom-set mishandles Custom Icon uploads. CSRF leads to upload of a ZIP archive containing a .php file.
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 privileges on the target site. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in WP SVG Icons < 3.2.3 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WP SVG Icons the fix is 3.2.3: builds < 3.2.3 are affected, anything from 3.2.3 onward is not.
Remediation
Update to version 3.2.3, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP SVG Icons: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP SVG Icons 3.2.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in WP SVG Icons
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C