CVE-2024-31422

Favicon <= 1.3.29 - Cross-Site Request Forgery to Notice Dismissal

2024-04-10 00:00
R3N0

Strategic Overview

Status
Patched in 1.3.30
Affected Plugin
Favicon by RealFaviconGenerator
Affected Version
<= 1.3.29
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-31422
View all Favicon by RealFaviconGenerator vulnerabilities

At a glance

CVE-2024-31422 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Favicon by RealFaviconGenerator WordPress plugin, affecting versions <= 1.3.29. 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 1.3.30; sites on affected versions should update now. Disclosed April 2024, reported by R3N0.

Vulnerability Overview

The Favicon plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.3.29. This is due to missing or incorrect nonce validation on the process_ignored_notice() function. This makes it possible for unauthenticated attackers to dismiss notices 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)

Favicon by RealFaviconGenerator <= 1.3.29 carries this weakness at process_ignored_notice(), 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 Favicon by RealFaviconGenerator the fix is 1.3.30: builds <= 1.3.29 are affected, anything from 1.3.30 onward is not.

Remediation

Update to version 1.3.30, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-31422https://www.wordfence.com/threat-intel/vulnerabilities/id/4a5d59da-dcac-44b4-a697-38eef650c6dehttps://nvd.nist.gov/vuln/detail/CVE-2024-31422

Related records

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