CVE-2023-2557

WPCS – WordPress Currency Switcher Professional <= 1.1.9 - Missing Authorization to Arbitrary Custom Drop-Down Currency Switcher Editing

2023-05-12 00:00
Alex Thomas

Strategic Overview

Status
Patched in 1.2.0
Affected Plugin
WPCS – WordPress Currency Switcher Professional
Affected Version
<= 1.1.9
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-2557
View all WPCS – WordPress Currency Switcher Professional vulnerabilities

At a glance

CVE-2023-2557 is a medium-severity Missing Authorization vulnerability in the WPCS WordPress plugin, affecting versions <= 1.1.9. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 1.2.0; sites on affected versions should update now. Disclosed May 2023, reported by Alex Thomas.

Vulnerability Overview

The WPCS – WordPress Currency Switcher Professional plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the save function in versions up to, and including, 1.1.9. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to edit an arbitrary custom drop-down currency switcher.

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

Reaching this weakness in WPCS <= 1.1.9 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 WPCS the fix is 1.2.0: builds <= 1.1.9 are affected, anything from 1.2.0 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-2557https://www.wordfence.com/threat-intel/vulnerabilities/id/d4c79242-5c89-40c0-abcc-c112f7a64a74https://nvd.nist.gov/vuln/detail/CVE-2023-2557

Related records

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