CVE-2023-47771

Essential Grid <= 3.0.18 - Missing Authorization

2023-11-14 00:00
Rafie Muhammad

Strategic Overview

Status
Patched in 3.0.19
Affected Version
<= 3.0.18
CVSS
8.3High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-47771
View all Essential Grid Portfolio – Photo Gallery vulnerabilities

At a glance

CVE-2023-47771 is a high-severity Missing Authorization vulnerability in the Essential Grid Portfolio WordPress plugin, affecting versions <= 3.0.18. It carries a CVSS score of 8.3 (reachable over the network; low attack complexity; high confidentiality, integrity impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 3.0.19; sites on affected versions should update now. Disclosed November 2023, reported by Rafie Muhammad.

Vulnerability Overview

The Essential Grid plugin for WordPress is vulnerable to unauthorized access of functionality due to a missing capability check on several functions in versions up to, and including, 3.0.18. This makes it possible for authenticated attackers, with subscriber-level access and above, to access those functions intended for higher privileged users. The exact consequences are not known.

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.

CWE-862: Missing Authorization

Reaching this weakness in Essential Grid Portfolio <= 3.0.18 takes a caller who can reach the endpoint. 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 Essential Grid Portfolio the fix is 3.0.19: builds <= 3.0.18 are affected, anything from 3.0.19 onward is not.

Remediation

Update to version 3.0.19, 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: Essential Grid Portfolio 3.0.19 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