# CVE-2022-1613: Restricted Site Access < 7.3.2 - Access Bypass via IP Spoofing

> Attackers can bypass IP-based access restrictions in the Restricted Site Access WordPress plugin by spoofing HTTP headers.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2022
- **Updated:** 21 May 2025
- **Also known as:** GHSA-5vpr-gfj6-pwh2

## What is CVE-2022-1613?

CVE-2022-1613 is a medium-severity authentication bypass vulnerability in Unknown Restricted Site Access, published on 26 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Restricted Site Access WordPress plugin before 7.3.2 prioritizes getting a visitor's IP from certain HTTP headers over PHP's REMOTE_ADDR, which makes it possible to bypass IP-based limitations in certain situations.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2022-1613?

It affects 1 product.


Products: 10up Restricted Site Access.

## How do I fix CVE-2022-1613?

No fix has been published for CVE-2022-1613 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-1613 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-1613 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1613 and fix it if it is affected.

What it is: CVE-2022-1613 is a medium-severity authentication bypass vulnerability in Unknown Restricted Site Access, published on 26 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-1613 exists.

Affected product: Unknown Restricted Site Access. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-1613/ (Markdown: https://insights.sbomify.com/CVE-2022-1613/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-1613
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-1613
- OSV: https://osv.dev/vulnerability/CVE-2022-1613

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-1613/
Summaries are generated and may contain mistakes; the official description above is the record.