Custom Fonts – Host Your Fonts Locally <= 2.1.16 - Missing Authorization to Unauthenticated Font Deletion
Strategic Overview
- Status
- Patched in 2.1.17
- Affected Plugin
- Custom Fonts – Host Your Fonts Locally
- Affected Version
<= 2.1.16- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-14351
At a glance
CVE-2025-14351 is a medium-severity Missing Authorization vulnerability in the Custom Fonts WordPress plugin, affecting versions <= 2.1.16. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.1.17; sites on affected versions should update now. Disclosed January 2026, reported by type5afe.
Vulnerability Overview
The Custom Fonts – Host Your Fonts Locally plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the 'BCF_Google_Fonts_Compatibility' class constructor function in all versions up to, and including, 2.1.16. This makes it possible for unauthenticated attackers to delete font directory and rewrite theme.json 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, and no interaction from a victim user.
CWE-862: Missing Authorization
Custom Fonts <= 2.1.16 carries this weakness at BCF_Google_Fonts_Compatibility, and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Custom Fonts the fix is 2.1.17: builds <= 2.1.16 are affected, anything from 2.1.17 onward is not.
Remediation
Update to version 2.1.17, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Custom Fonts 2.1.17 closes this, and updating the plugin is the step that ends it.
- Login Security
- 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