dbcve.org
Block For Font AwesomeWordPress extension · Getbutterfly

CVE-2024-35705

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-08
Fix available
A fix is available. Upgrade to 1.4.5 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Ciprian Popescu Block for Font Awesome allows Stored XSS.This issue affects Block for Font Awesome: from n/a through 1.4.4.

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

Stored XSS vulnerability in the Block for Font Awesome WordPress plugin allows authenticated attackers to inject malicious JavaScript through unsanitized input fields. The injected payload persists in the database and executes when administrators or other users view pages displaying the plugin's output.

MitigationUpdate to the latest version of Block for Font Awesome if available; otherwise, implement proper input sanitization using WordPress sanitization functions (sanitize_text_field, esc_attr) and output encoding (esc_html, esc_js) on all user-supplied values before rendering.

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
Block For Font AwesomeWordPress extension
Affected:< 1.4.5

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Check plugin version
    Navigate to WordPress Admin > Plugins > Block for Font Awesome and look at the version number, or run: wp plugin list --name='block-for-font-awesome'
    Affected if Version is lower than 1.4.5
  2. Verify plugin is active
    Confirm the Block for Font Awesome plugin is activated in WordPress Admin > Plugins
    Affected if Plugin is active and version is vulnerable
  3. Inspect plugin settings in database
    Query wp_options table for option_name containing 'block-for-font-awesome' or 'font_awesome': SELECT * FROM wp_options WHERE option_name LIKE '%font_awesome%' OR option_name LIKE '%block-for-font-awesome%'
    Affected if Any option values contain unescaped HTML script tags or javascript: URIs
  4. Check post meta for injected payloads
    Query wp_postmeta for meta_key containing 'font_awesome' and inspect meta_value for malicious scripts: SELECT * FROM wp_postmeta WHERE meta_key LIKE '%font_awesome%'
    Affected if Any meta_value contains <script> tags, event handlers (onclick, onerror, etc.), or javascript: prefixes
  5. Review widget/block configurations
    If using Gutenberg, check wp_posts for revision content with meta key '_wp_block_json' containing 'font-awesome', or inspect any custom widgets added via the plugin
    Affected if Stored configuration contains raw HTML or JavaScript in icon/fa fields

User is affected if Block for Font Awesome plugin version is below 1.4.5 and contains any unsanitized script payloads in plugin settings or post meta.

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

Update to the latest version of Block for Font Awesome if available; otherwise, implement proper input sanitization using WordPress sanitization functions (sanitize_text_field, esc_attr) and output encoding (esc_html, esc_js) on all user-supplied values before rendering.

Recommended fix High confidence

1.4.5

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Block for Font Awesome' in the plugin list
  4. Click 'Update now' if an update is available, or manually download version 1.4.5 from the WordPress plugin repository and upload it
  5. Verify the plugin version shows 1.4.5 after updating
  6. Test that Font Awesome blocks still function correctly on your site
  7. Clear any site caches if applicable

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

Fix this in Block For Font Awesome Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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