CVE-2026-2917: CWE-639 Authorization Bypass Through User-Controlled Key in thehappymonster Happy Addons for Elementor
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.
AI Analysis
Technical Summary
The Happy Addons for Elementor plugin suffers from an Insecure Direct Object Reference vulnerability (CWE-639) via the `ha_duplicate_thing` admin action handler. The authorization check uses `current_user_can('edit_posts')` which is a broad capability, instead of object-level checks like `current_user_can('edit_post', $post_id)`. Additionally, the nonce protecting the clone action is generic and not tied to a specific post ID, allowing attackers with Contributor or higher privileges to reuse a valid nonce from their own posts and change the `post_id` parameter to clone other users' posts. The cloning operation duplicates the entire post content, metadata (including sensitive widget configurations and API tokens), and taxonomies into a draft owned by the attacker. This can lead to unauthorized access to sensitive content and data within the WordPress environment.
Potential Impact
Authenticated users with Contributor-level access or higher can clone any published post, page, or custom post type regardless of ownership. This unauthorized cloning exposes potentially sensitive post content, metadata, widget configurations, and API tokens to the attacker. The vulnerability does not allow direct modification or deletion but compromises confidentiality by unauthorized duplication of content and associated data.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, restrict Contributor-level access where possible and monitor for unusual cloning activity. Avoid granting unnecessary edit permissions to untrusted users. Follow updates from thehappymonster for an official patch or temporary workaround.
CVE-2026-2917: CWE-639 Authorization Bypass Through User-Controlled Key in thehappymonster Happy Addons for Elementor
Description
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Happy Addons for Elementor plugin suffers from an Insecure Direct Object Reference vulnerability (CWE-639) via the `ha_duplicate_thing` admin action handler. The authorization check uses `current_user_can('edit_posts')` which is a broad capability, instead of object-level checks like `current_user_can('edit_post', $post_id)`. Additionally, the nonce protecting the clone action is generic and not tied to a specific post ID, allowing attackers with Contributor or higher privileges to reuse a valid nonce from their own posts and change the `post_id` parameter to clone other users' posts. The cloning operation duplicates the entire post content, metadata (including sensitive widget configurations and API tokens), and taxonomies into a draft owned by the attacker. This can lead to unauthorized access to sensitive content and data within the WordPress environment.
Potential Impact
Authenticated users with Contributor-level access or higher can clone any published post, page, or custom post type regardless of ownership. This unauthorized cloning exposes potentially sensitive post content, metadata, widget configurations, and API tokens to the attacker. The vulnerability does not allow direct modification or deletion but compromises confidentiality by unauthorized duplication of content and associated data.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, restrict Contributor-level access where possible and monitor for unusual cloning activity. Avoid granting unnecessary edit permissions to untrusted users. Follow updates from thehappymonster for an official patch or temporary workaround.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-02-20T20:58:53.545Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69b121032f860ef9435ba546
Added to database: 3/11/2026, 8:00:03 AM
Last enriched: 4/9/2026, 6:44:49 PM
Last updated: 4/24/2026, 3:12:50 PM
Views: 89
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.