dbcve.org
FontificWordPress extension · Andrei Ivasiuc

CVE-2024-27194

MEDIUM · 6.1 CVSS v3.1 Published 2024-03-16
Fix available
A fix is available. Upgrade to after 0.1.6 or later.
See remediation →
68/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 Andrei Ivasiuc Fontific | Google Fonts allows Stored XSS.This issue affects Fontific | Google Fonts: from n/a through 0.1.6.

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

A CSRF vulnerability in the Fontific | Google Fonts WordPress plugin (versions through 0.1.6) allows attackers to trick authenticated administrators into unknowingly submitting malicious requests that result in Stored XSS. The plugin lacks proper anti-CSRF token validation on its administrative forms, enabling attackers to inject malicious scripts that execute when other admins view the affected pages.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing administrative forms and validate these tokens on submission. Update to the patched version when available, or disable the plugin until remediation is complete.

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
FontificWordPress extension
Affected:<= 0.1.6

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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. Identify if Fontific plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'fontific' or 'fontific-google-fonts'. Alternatively, log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins to look for 'Fontific | Google Fonts' or similar naming.
    Affected if The plugin folder exists in wp-content/plugins/ or the plugin appears in the WordPress admin plugins list.
  2. Determine the installed version
    If the plugin is present, check its version number. In the WordPress admin, this is typically visible on the Plugins page under the plugin name. Alternatively, inspect the plugin's main PHP file or readme.txt in the plugin folder for a 'Version:' header.
    Affected if The version number is 0.1.6 or lower.
  3. Confirm the plugin is active
    In the WordPress admin dashboard, go to Plugins > Instored Plugins and verify whether the Fontific plugin is currently activated. Only active plugins can be exploited.
    Affected if The plugin shows as 'Active' in the WordPress admin.
  4. Inspect admin forms for CSRF protection
    Access the plugin settings pages in the WordPress admin (usually under Settings or a dedicated Fontific menu). View the page source (right-click > View Page Source) or inspect form elements to check if each form contains a wpnonce field (typically <input type="hidden" name="_wpnonce" ...> or similar nonce token).
    Affected if Administrative forms for the plugin lack _wpnonce or any anti-CSRF token field in the HTML.

The environment is affected if the Fontific | Google Fonts plugin (version 0.1.6 or lower) is installed, active, and its admin forms lack CSRF nonce tokens.

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.

From vendor data
Upgrade available Upgrade to a release after 0.1.6
Interim mitigation

Implement anti-CSRF tokens (nonces) on all state-changing administrative forms and validate these tokens on submission. Update to the patched version when available, or disable the plugin until remediation is complete.

Fix this in Fontific Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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