dbcve.org
Use Any FontWordPress extension · Dineshkarki

CVE-2024-47305

HIGH · 8.8 CVSS v3.1 Published 2024-09-25
Fix available
A fix is available. Upgrade to 6.3.09 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Dnesscarkey Use Any Font use-any-font allows Cross Site Request Forgery.This issue affects Use Any Font: from n/a through <= 6.3.08.

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Use Any Font WordPress plugin allows attackers to perform unauthorized actions on behalf of authenticated users by tricking them into visiting malicious pages. The plugin fails to properly validate anti-CSRF tokens on sensitive operations.

MitigationImplement WordPress nonces (wp_create_nonce/wp_verify_nonce) on all forms and AJAX endpoints within the plugin to validate request origin and prevent CSRF attacks.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Use Any FontWordPress extension
Affected:< 6.3.09

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Locate the Use Any Font plugin installation
    Navigate to the WordPress plugins directory (wp-content/plugins/) and locate the 'use-any-font' or 'dineshkarki-use-any-font' folder. Check the main plugin file (typically use-any-font.php) for the version header comment.
    Affected if The plugin folder or version header cannot be found, indicating the plugin may not be installed or has been removed.
  2. Read the installed plugin version
    Open the main plugin PHP file and locate the 'Version:' field in the plugin header comment at the top of the file. Record the version number displayed.
    Affected if No version number is found in the plugin header.
  3. Compare version against affected range
    Compare the installed version number to 6.3.09. Any version lower than 6.3.09 falls within the affected range.
    Affected if The installed version is less than 6.3.09 (for example, 6.3.08, 6.3.0, 6.2.0, etc.).
  4. Inspect source code for missing nonce validation (optional deeper check)
    Search the plugin PHP files for 'wp_verify_nonce', 'check_ajax_referer', or 'check_admin_referer' function calls. Specifically examine AJAX handlers and form processing code that perform state-changing operations such as font uploads, font activation, or settings updates.
    Affected if No nonce verification functions are found in the plugin code, or the identified state-changing operations lack nonce verification calls.

A user is affected if the Use Any Font plugin is installed with a version lower than 6.3.09 and the plugin handles font-related state-changing operations without proper anti-CSRF token validation.

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
Upgrade available Upgrade to 6.3.09 or later
Fixed in 6.3.09
Interim mitigation

Implement WordPress nonces (wp_create_nonce/wp_verify_nonce) on all forms and AJAX endpoints within the plugin to validate request origin and prevent CSRF attacks.

Recommended fix Moderate confidence

Use Any Font 6.3.09

  1. Log into the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Use Any Font' plugin
  4. Check if an update to version 6.3.09 or later is available
  5. If update available, click 'Update Now' to upgrade to version 6.3.09
  6. Alternatively, manually upload the version 6.3.09 plugin files via Plugins > Add New > Upload Plugin
  7. After update, verify the plugin version shows 6.3.09 or later

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

Fix this in Use Any Font Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47305 — 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-2024-47305 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