CVE-2022-38461

WPML <= 4.5.10 - Missing Authorization to Settings Change

2022-11-09 00:00
Dave Jong

Strategic Overview

Status
Patched in 4.5.11
Affected Plugin
WPML Multilingual CMS
Affected Version
<= 4.5.10
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2022-38461
View all WPML Multilingual CMS vulnerabilities

At a glance

CVE-2022-38461 is a medium-severity Missing Authorization vulnerability in the WPML Multilingual CMS WordPress plugin, affecting versions <= 4.5.10. 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 4.5.11; sites on affected versions should update now. Disclosed November 2022, reported by Dave Jong.

Vulnerability Overview

The WPML plugin for WordPress is vulnerable to missing authorization checks in versions up to, and including, 4.5.10. This is due to improper access controls on authorization for user controls. This makes it possible for subscriber-level attackers to perform plugin settings changes. This means allows the change of the language for legacy widgets, and the default behaviors for media content.

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 WPML Multilingual CMS <= 4.5.10 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 WPML Multilingual CMS the fix is 4.5.11: builds <= 4.5.10 are affected, anything from 4.5.11 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-38461https://www.wordfence.com/threat-intel/vulnerabilities/id/de62020b-5803-4ea7-89a1-24e5a512f2f3https://nvd.nist.gov/vuln/detail/CVE-2022-38461

Related records

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