Block For Font AwesomeWordPress extension · Getbutterfly
CVE-2023-49751
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Ciprian Popescu Block for Font Awesome.This issue affects Block for Font Awesome: from n/a through 1.4.0.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Block for Font Awesome WordPress plugin versions up to 1.4.0. The plugin lacks proper nonce validation on admin actions and form submissions, allowing attackers to trick authenticated administrators into performing unintended configuration changes or plugin modifications.
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
<= 1.4.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Block for Font Awesome plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Block for Font Awesome' or 'Getbutterfly Block For Font Awesome' in the listAffected if The plugin is present and active in the WordPress installation
-
Check installed version numberIn Plugins list, find the plugin and view the version number under the plugin name. Alternatively, check the plugin header in wp-content/plugins/block-for-font-awesome/block-for-font-awesome.php for 'Version:' valueAffected if Version is 1.4.0 or lower (the vulnerable version range)
-
Inspect admin form submissions for nonce fieldsView page source of any admin page under Settings > Font Awesome (or similar plugin settings page) and look for input fields with name containing 'nonce' or '_wpnonce'. Also check form tags for 'action' attributes that lack nonce field inclusionAffected if No nonce fields are present in admin forms, indicating the CSRF protection is missing
-
Inspect AJAX requests for nonce verificationCheck plugin PHP files in wp-content/plugins/block-for-font-awesome/ for AJAX handlers (wp_ajax_ hooks). Look for wp_verify_nonce or check_admin_referer calls at the beginning of these handler functionsAffected if AJAX handlers lack nonce verification calls, meaning CSRF protection is not enforced on AJAX actions
User is affected if the Block for Font Awesome plugin is installed with version 1.4.0 or lower AND admin forms/AJAX requests lack proper nonce validation.
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.
From vendor dataAdd WordPress nonces to all admin forms and AJAX requests, and verify these nonces on the server side before processing any state-changing operations.
Fix this in Block For Font Awesome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2023-49751 — 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-2023-49751 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