CVE-2023-1910

Getwid – Gutenberg Blocks <= 1.8.3 - Improper Authorization via get_remote_templates REST endpoint

2023-06-06 00:00
Ram

Strategic Overview

Status
Patched in 1.8.4
Affected Version
<= 1.8.3
CVSS
4.3Medium
Weakness type
CWE-285 · Improper Authorization
CVE
CVE-2023-1910
View all Getwid – Gutenberg Blocks vulnerabilities

At a glance

CVE-2023-1910 is a medium-severity Improper Authorization vulnerability in the Getwid WordPress plugin, affecting versions <= 1.8.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 1.8.4; sites on affected versions should update now. Disclosed June 2023, reported by Ram.

Vulnerability Overview

The Getwid – Gutenberg Blocks plugin for WordPress is vulnerable to unauthorized modification of data due to an insufficient capability check on the get_remote_templates function in versions up to, and including, 1.8.3. This makes it possible for authenticated attackers with subscriber-level permissions or above to flush the remote template cache. Cached template information can also be accessed via this endpoint but these are not considered sensitive as they are publicly accessible from the developer's site.

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-285: Improper Authorization

Reaching this weakness in Getwid <= 1.8.3 takes a caller who can reach the endpoint. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.

A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For Getwid the fix is 1.8.4: builds <= 1.8.3 are affected, anything from 1.8.4 onward is not.

Remediation

Update to version 1.8.4, 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: Getwid 1.8.4 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