JCH Optimize <= 4.0.0 - Missing Authorization to Authenticated (Subscriber+) Settings Modification

2023-08-08 00:00
Anonymous

Strategic Overview

Status
Patched in 4.0.1
Affected Plugin
JCH Optimize
Affected Version
< 4.0.1
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE pending
View all JCH Optimize vulnerabilities

At a glance

This record tracks a medium-severity Missing Authorization vulnerability in the JCH Optimize WordPress plugin, affecting versions < 4.0.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.0.1; sites on affected versions should update now. Disclosed August 2023.

Vulnerability Overview

The JCH Optimize plugin for WordPress is vulnerable to unauthorized modification of data due to missing capability checks on the doAjaxConfigureSettings(), doAjaxOptimizeImages(), doAjaxOnClickIcon(), and doAjaxSmartCombine() functions in versions up to, and including, 4.0.0. This makes it possible for authenticated attackers, with minimal permissions such as a subscriber, to modify and control plugin settings. CVE-2024-30481 is likely a duplicate of this issue.

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.

CWE-862: Missing Authorization

JCH Optimize < 4.0.1 carries this weakness at doAjaxConfigureSettings(), and reaching it takes an account at Subscriber level or above. 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 JCH Optimize the fix is 4.0.1: builds < 4.0.1 are affected, anything from 4.0.1 onward is not.

Remediation

Update to version 4.0.1, 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: JCH Optimize 4.0.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/2077bd81-52bd-4aa7-85f6-9abb02aec65b

Related records

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