dbcve.org
FontsWordPress extension · Fontsplugin

CVE-2024-43301

MEDIUM · 5.4 CVSS v3.1 Published 2024-08-26
Fix available
A fix is available. Upgrade to 3.7.8 or later.
See remediation →
61/100
Remediation priority · Elevated
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 Fonts Plugin Fonts allows Stored XSS.This issue affects Fonts: from n/a through 3.7.7.

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 vulnerability in the Fonts WordPress plugin allows authenticated administrators to be tricked into unknowingly storing malicious JavaScript code via forged requests. The lack of proper nonce validation on plugin settings forms enables attackers to craft malicious links that, when clicked by an admin, inject stored XSS into font-related pages.

MitigationImplement anti-CSRF nonce validation on all state-changing form submissions and admin actions in the plugin, and update to version 3.7.8 or later when available.

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
FontsWordPress extension
Affected:< 3.7.8

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/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. Verify Fonts plugin is installed
    Check the WordPress plugin directory or access Plugins > Installed Plugins in the WordPress admin dashboard and look for 'Fontsplugin Fonts' or 'Fonts' by Fontsplugin
    Affected if The plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the version number listed for the Fontsplugin Fonts plugin. Alternatively, inspect the plugin main file (typically in wp-content/plugins/fonts-plugin/includes or similar path) and look for the 'Version' header in the plugin comments
    Affected if The installed version is lower than 3.7.8
  3. Confirm admin access to plugin settings
    Log in as an administrator and navigate to the plugin settings page (usually under Settings > Fonts or a dedicated Fonts menu item in the left sidebar)
    Affected if The plugin settings page is accessible and allows configuration changes
  4. Check for missing nonce validation (manual code review)
    If you have access to the plugin source code, examine the form handling files (typically in the admin folder) and look for wp_nonce_field() or check_admin_referer() calls on form submissions. A vulnerable plugin will lack these nonce checks on settings save actions
    Affected if The plugin code lacks proper nonce validation on settings form submissions

A WordPress installation is affected if the Fontsplugin Fonts plugin versions below 3.7.8 are installed and the plugin settings are accessible to authenticated administrators.

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 3.7.8 or later
Fixed in 3.7.8
Interim mitigation

Implement anti-CSRF nonce validation on all state-changing form submissions and admin actions in the plugin, and update to version 3.7.8 or later when available.

Recommended fix Moderate confidence

3.7.8

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Fonts' (or 'Fonts Plugin') in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to version 3.7.8
  5. 5. Alternatively, navigate to Dashboard > Updates and select the Fonts plugin for update
  6. 6. After updating, verify the new version is 3.7.8 by checking the Plugins page
  7. 7. Test that the plugin functionality remains intact after the update

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

Fix this in Fonts 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-43301 — 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-43301 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