LiveActive security incident?Get immediate response
CVE Record

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

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.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A WordPress plugin used to restrict site access by visitor IP could be bypassed in versions before 7.3.2. The issue comes from trusting certain HTTP headers for the visitor IP instead of the server-provided address. This can weaken IP-based access controls.

Executive priority

Prioritize remediation for public WordPress sites where this plugin protects sensitive pages or administrative workflows. The issue is not rated critical, but it can undermine a business control if IP restriction is the only barrier.

Technical view

Restricted Site Access before 7.3.2 derives client IP from selected HTTP headers ahead of PHP REMOTE_ADDR. In affected deployments, that can let an unauthenticated remote user bypass IP-based limitations. CVSS 3.1 is 5.3: network, low complexity, no privileges, no user interaction, integrity impact only.

Likely exposure

Exposure is likely limited to WordPress sites running Restricted Site Access before 7.3.2 and relying on IP restrictions for access control. Sites not using this plugin, not using IP-based restrictions, or already updated are not indicated as affected by the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates unauthenticated network reachability and low attack complexity, but the bypass depends on deployment-specific IP handling conditions.

Researcher notes

The bundle identifies CWE-639, but the described root cause is client IP trust through HTTP headers. The affected-version data is inconsistent: the title and description say before 7.3.2, while one affected entry lists 7.3.2. Treat version scoping carefully.

Mitigation direction

  • Update Restricted Site Access to 7.3.2 or later.
  • Confirm WordPress plugin inventories across all managed sites.
  • Review vendor guidance before relying on alternative mitigations.
  • Avoid treating IP restriction as the only control for sensitive content.

Validation and detection

  • Identify sites with Restricted Site Access installed.
  • Confirm installed plugin versions are 7.3.2 or later.
  • Check whether restricted routes rely on IP-based allow or deny rules.
  • Review access logs for unexpected access to restricted content.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-1613 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2022-1613Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
UnknownRestricted Site Access7.3.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.