Custom Fonts · Security record
Is Custom Fonts safe?
No known vulnerability affects the current version (2.1.18). 2 issues were found in earlier versions and fixed, the latest disclosed on Jan 19, 2026.
Checked 4 days ago against the WPVulnerability database, for version 2.1.18.
How it’s looked after
- Last release
- Nov 4, 2026 (4 days ago)
- Releases in the last year
- 3
- Tested up to
- WordPress 7.1.4
- Support resolved
- 1 of 1 threads in two months
- Active installs
- 400K+
2 known vulnerabilities
- 2 medium
None affects the current version.
Disclosed each year
- 20241
- 20261
Every known vulnerability in Custom Fonts
Newest first, with any that affect the current version at the top.
Fixed in 2.1.17 · CVE-2025-14351 · Jan 19, 2026 · Wordfence
Fixed in 2.1.5 · CVE-2024-1332 · May 23, 2024 · Wordfence
Questions about Custom Fonts’s security
Is Custom Fonts safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Custom Fonts updated: most attacks target sites that haven’t updated.
Does Custom Fonts have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 2 older issues, fixed in earlier versions, so keep Custom Fonts up to date.
Is Custom Fonts still maintained?
Yes. Its last release was 4 days ago. Its authors resolved 1 of the 1 support threads opened in the last two months.
Is Custom Fonts compatible with the latest WordPress?
Yes. It’s tested up to WordPress 7.1.4, the current version.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.