All In One Favicon <= 4.7 - Authenticated(Admin+) Directory Traversal
Strategic Overview
- Status
- Patched in 4.8
- Affected Plugin
- All In One Favicon
- Affected Version
<= 4.7- CVSS
- 6.5Medium
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2023-24416
At a glance
CVE-2023-24416 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the All In One Favicon WordPress plugin, affecting versions <= 4.7. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 4.8; sites on affected versions should update now. Disclosed February 2023, reported by Kévin Mosbahi (Mika).
Vulnerability Overview
All In One Favicon plugin for WordPress is vulnerable to Directory Traversal via the 'aioFaviconUpdateSettings' function in versions up to, and including, 4.7. This allows authenticated attackers with administator-level permissions to delete arbitrary files on the site.
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 integrity, availability.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
All In One Favicon <= 4.7 carries this weakness at aioFaviconUpdateSettings, and reaching it takes an account at Admin level or above. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.
Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For All In One Favicon the fix is 4.8: builds <= 4.7 are affected, anything from 4.8 onward is not.
Remediation
Update to version 4.8, or a newer patched version
How does WordSec protect against this?
An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: All In One Favicon 4.8 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in All In One Favicon
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C