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

CVE-2026-2917

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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 Happy Addons for Elementor plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.21.0 via the `ha_duplicate_thing` admin action handler. This is due to the `can_clone()` method only checking `current_user_can('edit_posts')` (a general capability) without performing object-level authorization such as `current_user_can('edit_post', $post_id)`, and the nonce being tied to the generic action name `ha_duplicate_thing` rather than to a specific post ID. This makes it possible for authenticated attackers, with Contributor-level access and above, to clone any published post, page, or custom post type by obtaining a valid clone nonce from their own posts and changing the `post_id` parameter to target other users' content. The clone operation copies the full post content, all post metadata (including potentially sensitive widget configurations and API tokens), and taxonomies into a new draft owned by the attacker.

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 Happy Addons for Elementor plugin fails to perform object-level authorization when cloning posts. The `can_clone()` method only validates generic 'edit_posts' capability rather than checking if the user can edit the specific target post, and the nonce is tied to a generic action rather than the specific post ID being operated on. This allows any authenticated user with Contributor-level access to clone arbitrary published content by manipulating the post_id parameter.

MitigationImplement object-level authorization by adding `current_user_can('edit_post', $post_id)` checks and bind nonces to specific post IDs rather than generic action names.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 if Happy Addons for Elementor is installed
    Check your WordPress plugins directory or admin panel for 'Happy Addons for Elementor' and note its version number
    Affected if The plugin is installed and its version falls within the affected range (any version lacking object-level authorization checks in the cloning function)
  2. Determine if the post cloning feature is enabled
    Navigate to Happy Addons settings in the WordPress admin panel and locate the post cloning or 'Happy Clone' feature settings to see if it is activated
    Affected if The cloning feature is enabled, allowing the vulnerable code path to be reachable
  3. Review user role permissions for Contributor-level accounts
    In WordPress admin, go to Users > Roles or use a role management plugin to examine what capabilities Contributors possess; specifically check if they have access to the cloning functionality
    Affected if Contributor-level users or any role below Editor has permission to access the clone feature, enabling the exploitation path
  4. Inspect the can_clone() method implementation
    If you have code access, locate the Happy Addons plugin files and examine the can_clone() method (typically in includes/classes or similar); verify if it checks current_user_can('edit_post', $post_id) versus only checking generic 'edit_posts'
    Affected if The method only performs a generic capability check without verifying the user can edit the specific target post ID being cloned

You are affected if Happy Addons for Elementor is installed with the cloning feature enabled and the can_clone() method lacks post-specific authorization checks, allowing any Contributor to clone arbitrary published content.

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

Implement object-level authorization by adding `current_user_can('edit_post', $post_id)` checks and bind nonces to specific post IDs rather than generic action names.

Recommended fix Moderate confidence

3.21.1 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate 'Happy Addons for Elementor' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from wordpress.org and upload it via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the version number reflects 3.21.1 or higher

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-2917 — 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-2917 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