dbcve.org
Elegant Custom FontsWordPress extension · Breakdance

CVE-2023-27436

HIGH · 8.8 CVSS v3.1 Published 2023-11-13
Fix available
A fix is available. Upgrade to after 1.0 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 Louis Reingold Elegant Custom Fonts plugin <= 1.0 versions.

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 Elegant Custom Fonts WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions (such as modifying font settings) by forging malicious requests.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing admin actions and validate the referer header or origin header on POST requests.

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
Elegant Custom FontsWordPress extension
Affected:<= 1.0

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. Identify if Breakdance Elegant Custom Fonts plugin is installed
    Check the WordPress plugin directory for 'elegant-custom-fonts' or 'breakdance-elegant-custom-fonts' folder in wp-content/plugins
    Affected if The plugin folder exists in the plugins directory
  2. Determine the installed version of the plugin
    Read the main plugin file (usually index.php or main PHP file) and locate the version comment header, or check the plugin metadata via WordPress admin plugins page
    Affected if Version is 1.0 or any version lower than the fixed version
  3. Confirm the plugin is active
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, and verify if Elegant Custom Fonts is activated
    Affected if Plugin shows as Active in the plugins list
  4. Verify admin access to font settings is available
    Check if the Custom Fonts admin menu item exists under the Breakdance or Appearance menu in the WordPress admin dashboard
    Affected if The font settings admin interface is accessible to administrators

Environment is affected if Breakdance Elegant Custom Fonts plugin is installed, active, and version 1.0 or lower, with administrator access to the font settings page.

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 1.0
Interim mitigation

Implement anti-CSRF tokens (nonces) on all state-changing admin actions and validate the referer header or origin header on POST requests.

Fix this in Elegant Custom Fonts 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-2023-27436 — 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-2023-27436 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