dbcve.org
Restrict For ElementorWordPress extension · Restrict

CVE-2024-0910

MEDIUM · 5.3 CVSS v3.1 Published 2024-06-06
Fix available
A fix is available. Upgrade to 1.0.8 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Restrict for Elementor plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.0.7 due to improper restrictions on hidden data that make it accessible through the REST API. This makes it possible for unauthenticated attackers to extract potentially sensitive data from post content.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Restrict for Elementor WordPress plugin versions up to 1.0.7 improperly exposes hidden/restricted content through the REST API. The plugin's access restriction logic is not enforced on REST API endpoints, allowing unauthenticated attackers to retrieve sensitive post content that should be hidden.

MitigationUpdate the Restrict for Elementor plugin to a version beyond 1.0.7 if available, or implement server-side access controls to enforce authentication requirements on REST API endpoints serving restricted content.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Restrict For ElementorWordPress extension
Affected:< 1.0.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify plugin installation and version
    Locate the Restrict for Elementor plugin in your WordPress installation (typically in wp-content/plugins/) or check via WordPress admin panel under Plugins. Note the currently installed version number.
    Affected if The installed version is anything less than 1.0.8
  2. Confirm REST API is accessible without authentication
    Send a GET request to your site's REST API endpoint (for example, /wp-json/) without providing any authentication credentials. A successful response indicates the REST API is publicly accessible.
    Affected if The REST API responds to unauthenticated requests with full data rather than requiring authentication
  3. Test for exposed restricted content via REST API
    Identify a post or page that has content restricted by the plugin (check Elementor widget settings for Restrict functionality). Attempt to retrieve this content through REST API endpoints such as /wp-json/wp/v2/posts/{id} or /wp-json/wp/v2/pages/{id} without authentication.
    Affected if Restricted content that should be hidden is returned in the API response to unauthenticated users
  4. Check for plugin-specific REST endpoints
    Query the available REST API routes by accessing /wp-json/ and look for any endpoints related to the Restrict for Elementor plugin. Test these endpoints without authentication.
    Affected if Plugin-specific REST endpoints exist and return restricted data without authentication

You are affected if the Restrict for Elementor plugin version is below 1.0.8 AND your REST API returns restricted content to unauthenticated requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.8 or later
Fixed in 1.0.8
Interim mitigation

Update the Restrict for Elementor plugin to a version beyond 1.0.7 if available, or implement server-side access controls to enforce authentication requirements on REST API endpoints serving restricted content.

Recommended fix High confidence

1.0.8 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Restrict for Elementor' in the plugin list
  4. Verify current version is below 1.0.8
  5. If an update is available, click 'Update Now' to upgrade to version 1.0.8 or later
  6. Alternatively, download the latest version from wordpress.org and install via Plugins > Add New > Upload Plugin
  7. Confirm the update was successful by checking the installed version number

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Restrict For Elementor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0910 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-0910 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data