CVE-2022-1613

Restricted Site Access <= 7.3.1 - Access Bypass via IP Spoofing

2022-08-31 00:00
Daniel Ruf

Strategic Overview

Status
Patched in 7.3.2
Affected Plugin
Restricted Site Access
Affected Version
< 7.3.2
CVSS
6.5Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2022-1613
View all Restricted Site Access vulnerabilities

At a glance

CVE-2022-1613 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Restricted Site Access WordPress plugin, affecting versions < 7.3.2. 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 7.3.2; sites on affected versions should update now. Disclosed August 2022, reported by Daniel Ruf.

Vulnerability Overview

The Restricted Site Access plugin for WordPress is vulnerable to IP Spoofing in versions up to, and including, 7.3.1 due to prioritizing getting a visitor's IP from certain HTTP headers over PHP's REMOTE_ADDR. This makes it possible to bypass IP-based limitations in certain situations.

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-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Restricted Site Access < 7.3.2 takes a caller who can reach the endpoint. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Restricted Site Access the fix is 7.3.2: builds < 7.3.2 are affected, anything from 7.3.2 onward is not.

Remediation

Update to version 7.3.2, 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: Restricted Site Access 7.3.2 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