CVE-2024-47305

Use Any Font <= 6.3.08 - Cross-Site Request Forgery

2024-09-25 00:00
Rafie Muhammad

Strategic Overview

Status
Patched in 6.3.09
Affected Version
<= 6.3.08
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-47305
View all Use Any Font | Custom Font Uploader vulnerabilities

At a glance

CVE-2024-47305 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Use Any Font WordPress plugin, affecting versions <= 6.3.08. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.3.09; sites on affected versions should update now. Disclosed September 2024, reported by Rafie Muhammad.

Vulnerability Overview

The Use Any Font plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 6.3.08. This is due to missing or incorrect nonce validation on the uaf_trigger_actions() function. This makes it possible for unauthenticated attackers to update plugin settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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)

Use Any Font <= 6.3.08 carries this weakness at uaf_trigger_actions(), and reaching it 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.3.09: builds <= 6.3.08 are affected, anything from 6.3.09 onward is not.

Remediation

Update to version 6.3.09, 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.3.09 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