dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14351

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Custom Fonts plugin for WordPress has a missing capability check in the BCF_Google_Fonts_Compatibility class constructor, allowing unauthenticated attackers to delete font directories and rewrite the theme.json file. This is a broken access control vulnerability (CWE-862) where sensitive file operations lack authorization verification.

MitigationUpdate the plugin to version 2.1.17 or later which implements proper capability checks. Until then, consider restricting access at the server level or temporarily disabling the plugin if direct updates are not feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Custom Fonts plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'custom-fonts' or search for 'Custom Fonts' in the WordPress admin plugins list. Also inspect the main plugin file header for the version number.
    Affected if The plugin is installed and the version is unknown or below 2.1.17
  2. Locate the BCF_Google_Fonts_Compatibility class
    Search the plugin files for the class definition 'class BCF_Google_Fonts_Compatibility' - typically in includes/compatibility files. Inspect the constructor method to verify if capability checks are present.
    Affected if The class exists and its constructor lacks capability checks (e.g., no current_user_can() call before performing file operations)
  3. Verify file operation endpoints exist without authentication
    Search for AJAX actions or direct function calls within the BCF_Google_Fonts_Compatibility class that perform font directory deletion (like @rmdir or @unlink) and theme.json rewriting. Test if these endpoints respond without requiring WordPress login.
    Affected if The plugin exposes functions that delete font directories or modify theme.json without requiring authentication or capability verification
  4. Compare installed version to the patched release
    Extract the version from the plugin header comment (typically at the top of the main PHP file) and compare it to version 2.1.17.
    Affected if The installed version is lower than 2.1.17

A user is affected if the Custom Fonts plugin is installed with a version below 2.1.17 and the BCF_Google_Fonts_Compatibility class is present without capability checks in its constructor.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 2.1.17 or later which implements proper capability checks. Until then, consider restricting access at the server level or temporarily disabling the plugin if direct updates are not feasible.

Recommended fix Moderate confidence

Latest version after 2.1.16 (check wordpress.org for current stable release)

  1. Update the Custom Fonts – Host Your Fonts Locally plugin to the latest available version through the WordPress admin dashboard under Plugins > All Plugins > Update Now, or upload the latest version from wordpress.org/plugins/custom-fonts

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14351 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14351 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data