Plugins · custom-fonts · data as of 2026-11-01
Is Custom Fonts safe? Known vulnerabilities and latest version
- Latest version
- 2.1.17
- Last updated
- 2026-08-24
- Active installs
- 400,000+
- Known issues on record
- 2
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4
Custom Fonts is a powerful WordPress plugin that allows you to upload your own custom fonts or choose from a vast collection of Google Fonts, all host … — by Brainstorm Force
What to do
- Update to the latest version (2.1.17). Anything older than 2.1.17 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get custom-fonts --field=version shows what you run; wp plugin update custom-fonts updates it.
Check your version
Known vulnerabilities
2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 5.3 CVE-2025-14351 · published 2026-01-20
Missing authorization check in Custom Fonts (2.1.16 and older)
- Affected
- 2.1.16 and older
- Fixed in
- 2.1.17 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2025-14351Wordfence advisoryCode change (fix)Plugin source
medium 5.4 CVE-2024-1332 · published 2024-05-24
Stored cross-site scripting (XSS) in Custom Fonts (2.1.4 and older)
- Affected
- 2.1.4 and older
- Fixed in
- 2.1.5 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
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.
Recent activity
- 2026-08-24 — latest release on wordpress.org (2.1.17).
- 2026-01-20 — Missing authorization check disclosed (CVE-2025-14351), fixed in 2.1.17.
- 2024-05-24 — Stored cross-site scripting (XSS) disclosed (CVE-2024-1332), fixed in 2.1.5.
Get an email when Custom Fonts has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Custom Fonts (custom-fonts) is published or a fix ships. Unsubscribe in one click.
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/custom-fonts (Plugins API), fetched 2026-11-01.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-01. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/custom-fonts"><img src="https://laskyr.com/plugins/custom-fonts/badge.svg" alt="Custom Fonts vulnerability status"></a>