CVE-2023-45651

WP Attachments <= 5.0.11 - Cross-Site Request Forgery

2023-10-12 00:00
Abdi Pranata

Strategic Overview

Status
Patched in 5.0.12
Affected Plugin
WP Attachments
Affected Version
<= 5.0.11
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-45651
View all WP Attachments vulnerabilities

At a glance

CVE-2023-45651 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Attachments WordPress plugin, affecting versions <= 5.0.11. 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 5.0.12; sites on affected versions should update now. Disclosed October 2023, reported by Abdi Pranata.

Vulnerability Overview

The WP Attachments plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 5.0.11. This is due to missing or incorrect nonce validation on the wpatt_plugin_options function. This makes it possible for unauthenticated attackers to update plugin settings granted they can trick a site administrator into performing an action such as clicking on a link. The impact of this vulnerability is unknown.

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 WP Attachments <= 5.0.11 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 WP Attachments the fix is 5.0.12: builds <= 5.0.11 are affected, anything from 5.0.12 onward is not.

Remediation

Update to version 5.0.12, or a newer patched version

How does WordSec protect against this?

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