Better Font AwesomeWordPress extension · Better Font Awesome Project
CVE-2022-37405
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 Mickey Kay's Better Font Awesome plugin <= 2.0.1 at WordPress.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Better Font Awesome WordPress plugin versions 2.0.1 and below allows attackers to trick authenticated administrators into performing unintended plugin actions via malicious requests, as the plugin lacks proper CSRF token validation.
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
Better Font AwesomeWordPress extension
<= 2.0.1CVSS 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 Better Font Awesome plugin is installedLog into WordPress admin panel, navigate to Plugins > Installed Plugins, and locate Better Font Awesome in the list. Note whether it is active or inactive.Affected if Plugin is active and installed with version 2.0.1 or below
-
Check installed plugin versionIn the Plugins list in WordPress admin, click on the plugin name or view the plugin details to find the version number displayed. Compare this against the affected range of <= 2.0.1.Affected if Installed version is 2.0.1 or lower, or version cannot be verified but plugin is present
-
Inspect plugin for CSRF protection mechanismsAccess the plugin files via FTP or file manager. Examine the main plugin PHP file (typically better-font-awesome.php) and any files handling form submissions or AJAX actions. Search for presence of WordPress nonce verification functions such as wp_nonce_field, wp_nonce_url, check_admin_referer, or check_ajax_referer.Affected if Plugin code lacks nonce verification on admin actions, form submissions, or AJAX endpoints
-
Identify unprotected admin actionsReview plugin PHP files for action hooks handling admin requests (admin_post_, wp_ajax_, or similar). Check if these handlers verify user permissions and validate nonces before processing requests.Affected if Admin action handlers exist without wp_nonce verification or capability checks
The environment is affected if the Better Font Awesome plugin is active with version 2.0.1 or below, or if the plugin code is present and lacks CSRF token validation on its form submissions and AJAX actions.
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 dataUpdate the Better Font Awesome plugin to a version newer than 2.0.1. If no patched version is available, remove the plugin until a fix is released, or manually implement WordPress nonce verification on all form submissions and AJAX actions within the plugin.
Fix this in Better 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-2022-37405 — 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-2022-37405 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