CVE-2023-4243

FULL - Customer <= 2.2.3 - Authenticated(Subscriber+) Improper Authorization to Arbitrary Plugin Installation

2023-08-08 00:00
Ram

Strategic Overview

Status
Patched in 2.3
Affected Plugin
FULL – Cliente
Affected Version
<= 2.2.3
CVSS
8.8High
Weakness type
CWE-285 · Improper Authorization
CVE
CVE-2023-4243
View all FULL – Cliente vulnerabilities

At a glance

CVE-2023-4243 is a high-severity Improper Authorization vulnerability in the FULL WordPress plugin, affecting versions <= 2.2.3. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.3; sites on affected versions should update now. Disclosed August 2023, reported by Ram.

Vulnerability Overview

The FULL - Customer plugin for WordPress is vulnerable to Arbitrary File Upload via the /install-plugin REST route in versions up to, and including, 2.2.3 due to improper authorization. This allows authenticated attackers with subscriber-level permissions and above to execute code by installing plugins from arbitrary remote locations including non-repository sources onto the site, granted they are packaged as a valid WordPress plugin.

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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-285: Improper Authorization

Reaching this weakness in FULL <= 2.2.3 takes an account at Subscriber level or above. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.

A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For FULL the fix is 2.3: builds <= 2.2.3 are affected, anything from 2.3 onward is not.

Remediation

Update to version 2.3, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: FULL 2.3 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