CVE-2022-27851

Use Any Font <= 6.1.7 - Cross-Site Request Forgery to API Key Deactivation

2022-03-30 11:53
Rasi Afeef

Strategic Overview

Status
Patched in 6.1.8
Affected Version
<= 6.1.7
CVSS
5.4Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2022-27851
View all Use Any Font | Custom Font Uploader vulnerabilities

At a glance

CVE-2022-27851 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Use Any Font WordPress plugin, affecting versions <= 6.1.7. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.1.8; sites on affected versions should update now. Disclosed March 2022, reported by Rasi Afeef.

Vulnerability Overview

Cross-Site Request Forgery (CSRF) in Use Any Font (WordPress plugin) <= 6.1.7 allows an attacker to deactivate the API key.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Use Any Font <= 6.1.7 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Use Any Font the fix is 6.1.8: builds <= 6.1.7 are affected, anything from 6.1.8 onward is not.

Remediation

Update to version 6.1.8, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Use Any Font: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Use Any Font 6.1.8 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C