CVE-2022-1956

Shortcut Macros <= 1.3 - Missing Authorization to Settings Update

2022-06-16 00:00
Daniel Ruf

Strategic Overview

Status
Unpatched
Affected Plugin
Shortcut Macros
Affected Version
<= 1.3
CVSS
5.4Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2022-1956
View all Shortcut Macros vulnerabilities

At a glance

CVE-2022-1956 is a medium-severity Missing Authorization vulnerability in the Shortcut Macros WordPress plugin, affecting versions <= 1.3. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed June 2022, reported by Daniel Ruf.

Vulnerability Overview

The Shortcut Macros WordPress plugin through 1.3 does not have authorisation and CSRF checks in place when updating its settings, which could allow any authenticated users, such as subscriber, to update them.

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 Shortcut Macros <= 1.3 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. No fixed build of this plugin is recorded for Shortcut Macros yet, so installs running <= 1.3 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Login Security
  • Alerts

External References

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