CVE-2022-0952

Sitemap by click5 <= 1.0.35 - Unauthenticated Arbitrary Options Update

2022-04-13 00:00
cydave

Strategic Overview

Status
Patched in 1.0.36
Affected Plugin
Sitemap by click5
Affected Version
<= 1.0.35
CVSS
6.5Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2022-0952
View all Sitemap by click5 vulnerabilities

At a glance

CVE-2022-0952 is a medium-severity Missing Authorization vulnerability in the Sitemap by click5 WordPress plugin, affecting versions <= 1.0.35. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.0.36; sites on affected versions should update now. Disclosed April 2022, reported by cydave.

Vulnerability Overview

The Sitemap by click5 WordPress plugin before 1.0.36 does not have authorisation and CSRF checks when updating options via a REST endpoint, and does not ensure that the option to be updated belongs to the plugin. As a result, unauthenticated attackers could change arbitrary blog options, such as the users_can_register and default_role, allowing them to create a new admin account and take over the blog.

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

Reaching this weakness in Sitemap by click5 <= 1.0.35 takes no account at all. 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 Sitemap by click5 the fix is 1.0.36: builds <= 1.0.35 are affected, anything from 1.0.36 onward is not.

Remediation

Update to version 1.0.36, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Sitemap by click5 1.0.36 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

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