FontsWordPress extension · Fontsplugin
CVE-2024-43302
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 · uneditedMissing Authorization vulnerability in Fonts Plugin Fonts allows Exploiting Incorrectly Configured Access Control Security Levels.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 confidenceMissing authorization vulnerability in the Fonts plugin allows attackers to exploit incorrectly configured access control security levels. This likely enables unauthorized users to access privileged administrative functions or perform actions beyond their permitted scope due to missing capability checks on certain endpoints.
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
< 3.7.8CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Fonts plugin is installedNavigate to WordPress admin dashboard > Plugins and locate the Fonts plugin by Fontsplugin, or check the plugin files in /wp-content/plugins/ for the fontsplugin-fonts directoryAffected if The Fonts plugin is present in the WordPress installation
-
Determine installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Fontsplugin Fonts and read the version number displayed under the plugin name, or check the version in the plugin's main PHP file headerAffected if The version number is less than 3.7.8 (e.g., 3.7.7, 3.6.x, etc.)
-
Identify exposed administrative endpointsReview plugin source code for registered REST API routes or admin AJAX handlers. Check files such as class-fonts-plugin.php or any API-related PHP files in the plugin directory for add_action calls on 'rest_api_init' or 'admin_post_' hooksAffected if The plugin registers REST API endpoints or admin POST handlers without capability checks (missing current_user_can() or similar authorization calls)
-
Test endpoint authorizationIf REST API endpoints exist, attempt to access them using a low-privilege user account (subscriber or contributor role) without proper administrative capabilitiesAffected if Low-privilege users can successfully access endpoints that should require administrator-level permissions
The environment is affected if the Fontsplugin Fonts plugin version is below 3.7.8 AND the plugin exposes administrative endpoints that lack proper capability verification checks.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.7.8
Update the Fonts plugin to the latest patched version and review all plugin endpoints for proper authorization enforcement.
3.7.8
- Backup your WordPress site before making any changes
- Navigate to Plugins > All Plugins in the WordPress admin dashboard
- Locate the Fonts plugin in the list
- Click 'Update now' if an update is available, or manually update to version 3.7.8
- After updating, verify the plugin version shows 3.7.8
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fonts
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43302 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-43302 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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