dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-7665

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Essential Addons for Elementor – Popular Elementor Templates & Widgets plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 6.6.4 via the ajax_load_more function due to insufficient restrictions on which posts can be included. This makes it possible for unauthenticated attackers to extract data from password protected, private, or draft posts that they should not have access to.

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 Essential Addons for Elementor plugin versions up to 6.6.4 has an Information Exposure vulnerability in its ajax_load_more function. The function fails to properly validate user authorization before returning post content, allowing unauthenticated attackers to extract sensitive data from password-protected, private, or draft posts that should be restricted.

MitigationUpdate the Essential Addons for Elementor plugin to a version beyond 6.6.4 that includes proper authorization checks in the ajax_load_more function, or implement access control logic to verify user permissions before returning post data.

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

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. Verify Essential Addons for Elementor is installed
    Navigate to WordPress admin > Plugins and confirm 'Essential Addons for Elementor' is installed and active, or query the database: SELECT option_value FROM wp_options WHERE option_name = 'plugin' AND option_value LIKE '%elementor%'
    Affected if The plugin is installed and active
  2. Determine installed plugin version
    In WordPress admin > Plugins > Essential Addons for Elementor, view the plugin details to see the version number, or check the plugin header in wp-content/plugins/essential-addons-for-elementor/includes/index.php or the main plugin file
    Affected if Version is below 6.6.5 (the patched version)
  3. Identify if ajax_load_more functionality is in use
    Check if the plugin's ajax_load_more feature is enabled by reviewing the plugin settings in Essential Addons > Settings > Post Grid / Custom', or search the database for postmeta entries with meta_key like '%ea_elementor_ajax_load_more%'
    Affected if The ajax_load_more feature is enabled and the plugin version is below 6.6.5
  4. Inspect ajax_load_more function for authorization gap
    Examine the file wp-content/plugins/essential-addons-for-elementor/includes/.../ajax-load-more.php (path varies by version) and verify the function lacks a check like current_user_can('edit_post', $post_id) or proper post visibility validation before returning post content
    Affected if The function returns post content without verifying user permissions or post status (password protected, private, draft)
  5. Confirm presence of sensitive post types
    Query the database: SELECT ID, post_title, post_status, post_password FROM wp_posts WHERE post_status IN ('private', 'draft', 'publish') OR post_password != ''
    Affected if There are private, draft, or password-protected posts on the site and the plugin version is vulnerable

You are affected if Essential Addons for Elementor is installed with version below 6.6.5, the ajax_load_more feature is enabled, and your site contains private, draft, or password-protected posts.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Essential Addons for Elementor plugin to a version beyond 6.6.4 that includes proper authorization checks in the ajax_load_more function, or implement access control logic to verify user permissions before returning post data.

Recommended fix Moderate confidence

Essential Addons for Elementor version 6.6.5 or later (verify latest version on wordpress.org)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Essential Addons for Elementor' in the plugin list
  4. Check if current version is 6.6.4 or earlier
  5. If vulnerable, click 'Update Now' to install the latest version
  6. Alternatively, download the latest version from wordpress.org/plugins/essential-addons-for-elementor/ and upload manually
  7. After update, verify the new version number in the plugins list

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7665 — 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-2026-7665 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