CVE-2024-43116

Simple Local Avatars <= 2.7.10 - Cross-Site Request Forgery via save_default_avatar_file_id()

2024-08-07 00:00
Rafie Muhammad

Strategic Overview

Status
Patched in 2.7.11
Affected Plugin
Simple Local Avatars
Affected Version
<= 2.7.10
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-43116
View all Simple Local Avatars vulnerabilities

At a glance

CVE-2024-43116 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Simple Local Avatars WordPress plugin, affecting versions <= 2.7.10. 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 2.7.11; sites on affected versions should update now. Disclosed August 2024, reported by Rafie Muhammad.

Vulnerability Overview

The Simple Local Avatars plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.7.10. This is due to missing or incorrect nonce validation on the save_default_avatar_file_id() function. This makes it possible for unauthenticated attackers to set the default avatar file 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)

Simple Local Avatars <= 2.7.10 carries this weakness at save_default_avatar_file_id(), 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 Simple Local Avatars the fix is 2.7.11: builds <= 2.7.10 are affected, anything from 2.7.11 onward is not.

Remediation

Update to version 2.7.11, or a newer patched version

How does WordSec protect against this?

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