CVE-2021-24935

WP Google Fonts <= 3.1.4 - Reflected Cross-Site Scripting

2021-11-03 00:00
ZhongFu Su

Strategic Overview

Status
Patched in 3.1.5
Affected Plugin
WP Google Fonts
Affected Version
<= 3.1.4
CVSS
6.1Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2021-24935
View all WP Google Fonts vulnerabilities

At a glance

CVE-2021-24935 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WP Google Fonts WordPress plugin, affecting versions <= 3.1.4. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.1.5; sites on affected versions should update now. Disclosed November 2021, reported by ZhongFu Su.

Vulnerability Overview

The WP Google Fonts WordPress plugin before 3.1.5 does not escape the googlefont_ajax_name and googlefont_ajax_family parameter of the googlefont_action AJAx action (available to any authenticated user) before outputing them in attributes, leading Reflected Cross-Site Scripting issues

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-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in WP Google Fonts <= 3.1.4 takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For WP Google Fonts the fix is 3.1.5: builds <= 3.1.4 are affected, anything from 3.1.5 onward is not.

Remediation

Update to version 3.1.5, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WP Google Fonts: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Google Fonts 3.1.5 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