Favicon Generator <= 1.5 - Cross-Site Request Forgery to Arbitrary File Deletion
Strategic Overview
- Status
- Patched in 2.1
- Affected Plugin
- Favicon Generator (CLOSED)
- Affected Version
<= 1.5- CVSS
- 9.6Critical
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-7568
At a glance
CVE-2024-7568 is a critical-severity Cross-Site Request Forgery (CSRF) vulnerability in the Favicon Generator (CLOSED) WordPress plugin, affecting versions <= 1.5. It carries a CVSS score of 9.6 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.1; sites on affected versions should update now. Disclosed August 2024, reported by Marco Wotschka.
Vulnerability Overview
The Favicon Generator plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.5. This is due to missing or incorrect nonce validation on the output_sub_admin_page_0 function. This makes it possible for unauthenticated attackers to delete arbitrary files on the server via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. The plugin author deleted the functionality of the plugin to patch this issue and close the plugin, we recommend seeking an alternative to this plugin. CVE-2024-7864 appears to be a duplicate of this issue.
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 Favicon Generator (CLOSED) <= 1.5 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 Favicon Generator (CLOSED) the fix is 2.1: builds <= 1.5 are affected, anything from 2.1 onward is not.
Remediation
Update to version 2.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Favicon Generator (CLOSED): WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Favicon Generator (CLOSED) 2.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C