dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-1800

HIGH · 7.5 CVSS v3.1 Published 2026-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 Fonts Manager | Custom Fonts plugin for WordPress is vulnerable to time-based SQL Injection via the ‘fmcfIdSelectedFnt’ parameter in all versions up to, and including, 1.2 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 Fonts Manager | Custom Fonts WordPress plugin (versions up to 1.2) contains a time-based SQL injection vulnerability in the 'fmcfIdSelectedFnt' parameter. An unauthenticated attacker can inject malicious SQL queries due to insufficient input sanitization and lack of prepared statements in the database query, allowing extraction of sensitive data from the database.

MitigationUpdate to the latest version of the plugin (beyond 1.2) which should contain proper input sanitization and prepared SQL statements. As a temporary measure, consider deploying a WAF rule to block requests with suspicious SQL patterns in the fmcfIdSelectedFnt parameter.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 the plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'fonts-manager-custom-fonts' or similar. Also check via WordPress admin dashboard under Plugins > Installed Plugins.
    Affected if The plugin folder exists in wp-content/plugins/ and appears in the WordPress plugins list.
  2. Determine the installed plugin version
    Open the plugin's main PHP file (usually named 'fonts-manager-custom-fonts.php') or the 'readme.txt' file in the plugin directory and look for the 'Version' header comment.
    Affected if The reported version is 1.2 or any version number lower than 1.2 (e.g., 1.0, 1.1).
  3. Confirm the plugin is active
    Check the WordPress database 'wp_options' table for the option 'active_plugins', or view the plugin status in the WordPress admin Plugins page.
    Affected if The plugin shows as 'Active' in WordPress rather than 'Inactive' or 'Network Active'.
  4. Identify the vulnerable endpoint
    Search the plugin PHP files for the string 'fmcfIdSelectedFnt' to locate the file and function handling this parameter. This parameter is likely received via GET or POST request.
    Affected if The parameter 'fmcfIdSelectedFnt' is found in a plugin PHP file and is used directly in a database query without prepare() statements.
  5. Inspect the vulnerable query code
    Examine the code around the fmcfIdSelectedFnt parameter usage. Look for wpdb->prepare() or $wpdb->prepare() calls. If absent and the parameter is concatenated directly into SQL, the vulnerability is present.
    Affected if The code does not use prepared statements ($wpdb->prepare) and the parameter is inserted directly into the SQL query without sanitization functions like sanitize_text_field().

You are affected if the Fonts Manager plugin is installed, active, and running version 1.2 or lower, with the fmcfIdSelectedFnt parameter being used in unsanitized SQL queries.

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 to the latest version of the plugin (beyond 1.2) which should contain proper input sanitization and prepared SQL statements. As a temporary measure, consider deploying a WAF rule to block requests with suspicious SQL patterns in the fmcfIdSelectedFnt parameter.

Recommended fix High confidence

Version 1.3 or later of Fonts Manager | Custom Fonts plugin

  1. Update the Fonts Manager | Custom Fonts WordPress plugin to version 1.3 or later

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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