CVE-2023-48757

JetEngine <= 3.2.4 - Authenticated (Contributor+) Privilege Escalation

2023-11-28 00:00
Rafie Muhammad

Strategic Overview

Status
Patched in 3.2.5
Affected Plugin
JetEngine
Affected Version
<= 3.2.4
CVSS
8.8High
Weakness type
CWE-284 · Improper Access Control
CVE
CVE-2023-48757
View all JetEngine vulnerabilities

At a glance

CVE-2023-48757 is a high-severity Improper Access Control vulnerability in the JetEngine WordPress plugin, affecting versions <= 3.2.4. 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 Contributor level or above. The issue is fixed in version 3.2.5; sites on affected versions should update now. Disclosed November 2023, reported by Rafie Muhammad.

Vulnerability Overview

The JetEngine plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 3.2.4. This is due to an unknown issue. This makes it possible for authenticated attackers, with contributor-level access and above, to gain elevated privileges.

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-284: Improper Access Control

Reaching this weakness in JetEngine <= 3.2.4 takes an account at Contributor level or above. Improper access control means the code decides what a caller may do using something other than their actual permissions, so the decision can be wrong without any check appearing to be missing.

Whoever can shape the request decides the answer, so the protected action runs for callers the code never meant to allow. For JetEngine the fix is 3.2.5: builds <= 3.2.4 are affected, anything from 3.2.5 onward is not.

Remediation

Update to version 3.2.5, 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: JetEngine 3.2.5 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