Custom Fonts – Host Your Fonts Locally <= 2.1.4 - Authenticated (Author+) Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 2.1.5
- Affected Plugin
- Custom Fonts – Host Your Fonts Locally
- Affected Version
<= 2.1.4- CVSS
- 6.4Medium
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2024-1332
At a glance
CVE-2024-1332 is a medium-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Custom Fonts WordPress plugin, affecting versions <= 2.1.4. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 2.1.5; sites on affected versions should update now. Disclosed May 2024, reported by James Myers (ConfidenceRemainsHigh).
Vulnerability Overview
The Custom Fonts – Host Your Fonts Locally plugin for WordPress is vulnerable to Stored Cross-Site Scripting via svg file upload in all versions up to, and including, 2.1.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author level or higher, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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.
CWE-434: Unrestricted Upload of File with Dangerous Type
Reaching this weakness in Custom Fonts <= 2.1.4 takes an account at Author level or above. 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 Custom Fonts the fix is 2.1.5: builds <= 2.1.4 are affected, anything from 2.1.5 onward is not.
Remediation
Update to version 2.1.5, or a newer patched version
How does WordSec protect against this?
An attacker needs Author 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. 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: Custom Fonts 2.1.5 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Other vulnerabilities in Custom Fonts – Host Your Fonts Locally
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C