LiveActive security incident?Get immediate response
CVE Record

CVE-2024-24702: WordPress Page Restrict Plugin <= 2.5.5 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Matt Martz & Andy Stratton Page Restrict.This issue affects Page Restrict: from n/a through 2.5.5.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-24702 is a CSRF issue in the WordPress Page Restrict plugin through version 2.5.5. A victim would need to interact with attacker-controlled content. The published impact is limited integrity impact, not data disclosure or service outage.

Executive priority

Treat as a moderate WordPress hygiene issue. Prioritize sites where Page Restrict controls access to sensitive content or where administrators frequently work from persistent logged-in browser sessions.

Technical view

The source bundle identifies CWE-352 Cross-Site Request Forgery in Matt Martz & Andy Stratton Page Restrict, package pagerestrict, affecting versions through 2.5.5. CVSS 3.1 is 4.3 with network attack vector, low complexity, no attacker privileges, required user interaction, and low integrity impact.

Likely exposure

Exposure is limited to WordPress sites with Page Restrict installed at version 2.5.5 or earlier. Actual business risk depends on which plugin action lacks CSRF protection and the permissions of the targeted logged-in user.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. CSRF generally depends on tricking a logged-in user into interacting with attacker-controlled content; the bundle does not describe exploit mechanics or affected actions.

Researcher notes

Evidence is sufficient for affected product, vulnerability class, CVSS, and version ceiling. The bundle does not identify a fixed version, specific vulnerable endpoint, proof of exploitation, or detailed impact path, so validation should remain inventory-driven and source-grounded.

Mitigation direction

  • Inventory WordPress sites for the Page Restrict plugin and its version.
  • Check vendor or Patchstack guidance for a fixed release before updating.
  • Disable or remove the plugin if no supported fixed version is available.
  • Limit WordPress administrator browsing from privileged logged-in sessions.
  • Use MFA and least-privilege roles for WordPress administrative accounts.

Validation and detection

  • Confirm whether Page Restrict is installed on each WordPress site.
  • Record the installed version and flag 2.5.5 or earlier.
  • Review vendor or Patchstack advisories for fixed-version status.
  • Check recent plugin configuration or content changes for unauthorized modifications.
  • Verify remediation by confirming the plugin is updated, disabled, or removed.
Prepared
Confidence
medium
Sources
3

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 · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-2024-24702 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
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2024-24702Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Matt Martz & Andy StrattonPage Restrictpagerestrict, n/aunaffected
Weakness

CWE details

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