CVE-2023-40200

Multiple WPOnlineSupport Plugins <= (Various Versions) - Missing Authorization to Notice Dismissal

2023-08-16 00:00
Abdi Pranata

Strategic Overview

Status
Patched in 1.5
Affected Plugin
Featured Post Creative
Affected Version
<= 1.4
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-40200
View all Featured Post Creative vulnerabilities

At a glance

CVE-2023-40200 is a medium-severity Missing Authorization vulnerability in the Featured Post Creative WordPress plugin, affecting versions <= 1.4. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.5; sites on affected versions should update now. Disclosed August 2023, reported by Abdi Pranata.

Vulnerability Overview

Multiple WPOnlineSupport plugins for WordPress are vulnerable to unauthorized modification of data due to a missing capability check on the wpos_anylc_admin_init_process() function hooked via admin_init in various versions. This makes it possible for unauthenticated attackers to dismiss a license notice.

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 privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Featured Post Creative <= 1.4 carries this weakness at wpos_anylc_admin_init_process(), and reaching it 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 Featured Post Creative the fix is 1.5: builds <= 1.4 are affected, anything from 1.5 onward is not.

Remediation

Update to version 1.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: Featured Post Creative 1.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