CVE-2024-12300

AR for WordPress <= 7.3 - Missing Authorization to Unauthenticated Limited File Upload

2024-12-12 14:54
cc

Strategic Overview

Status
Patched in 7.4
Affected Plugin
AR for WordPress
Affected Version
<= 7.3
CVSS
3.7Low
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-12300
View all AR for WordPress vulnerabilities

At a glance

CVE-2024-12300 is a low-severity Missing Authorization vulnerability in the AR for WordPress WordPress plugin, affecting versions <= 7.3. It carries a CVSS score of 3.7 (reachable over the network). Exploitation requires no authentication. The issue is fixed in version 7.4; sites on affected versions should update now. Disclosed December 2024, reported by cc.

Vulnerability Overview

The AR for WordPress plugin for WordPress is vulnerable to unauthorized double extension file upload due to a missing capability check on the set_ar_featured_image() function in all versions up to, and including, 7.3. This makes it possible for unauthenticated attackers to upload php files leveraging a double extension attack. It's important to note the file is deleted immediately and double extension attacks only work on select servers making this unlikely to be successfully exploited.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

AR for WordPress <= 7.3 carries this weakness at set_ar_featured_image(), and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For AR for WordPress the fix is 7.4: builds <= 7.3 are affected, anything from 7.4 onward is not.

Remediation

Update to version 7.4, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: AR for WordPress 7.4 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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