LiveActive security incident?Get immediate response
CVE Record

CVE-2022-37405: WordPress Better Font Awesome plugin <= 2.0.1 - Cross-Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in Mickey Kay's Better Font Awesome plugin <= 2.0.1 at WordPress.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-37405 is a CSRF issue in the Better Font Awesome WordPress plugin through version 2.0.1. It could let an attacker trick a user into performing an unintended action in WordPress. The documented impact is limited integrity loss, not data theft or outage.

Executive priority

Treat as a moderate WordPress hygiene item. It is not documented as actively exploited here, but affected public sites should be identified and remediated during the next normal vulnerability cycle.

Technical view

The source data identifies CWE-352 in Mickey Kay's Better Font Awesome plugin <= 2.0.1. CVSS 3.1 is 4.3 with network attack vector, low complexity, no attacker privileges, required user interaction, unchanged scope, low integrity impact, and no confidentiality or availability impact.

Likely exposure

Exposure is limited to WordPress sites with Better Font Awesome installed at version 2.0.1 or earlier. The bundle provides no CPEs and no hosting-specific indicators, so asset inventory is required.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not state active exploitation. The CVSS vector indicates exploitation requires user interaction and affects integrity only at a low level.

Researcher notes

Evidence is narrow: the bundle confirms product, affected version range, CWE, CVSS, and references, but not exploit details, exact vulnerable action, or fixed version. Avoid assuming broader WordPress or theme exposure.

Mitigation direction

  • Inventory WordPress sites for the Better Font Awesome plugin.
  • Confirm whether installed versions are 2.0.1 or earlier.
  • Review WordPress.org and Patchstack for fixed release or vendor guidance.
  • If still affected, disable or remove the plugin after business review.
  • Prioritize remediation on externally managed or high-trust WordPress sites.

Validation and detection

  • Check plugin name and version in WordPress administration or asset inventory.
  • Verify findings against the affected range: Better Font Awesome <= 2.0.1.
  • Review change records for plugin update, removal, or compensating decision.
  • Confirm no unapproved affected instances remain in production.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-37405 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2022-37405Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Mickey KayBetter Font Awesome (WordPress plugin)<= 2.0.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.