Security readout for executives and security teams
Plain-English summary
CVE-2026-2917 affects the Happy Addons for Elementor WordPress plugin through version 3.21.0. A logged-in Contributor or higher user could duplicate content they should not control, including pages, custom posts, metadata, taxonomies, and possibly sensitive widget settings or API tokens. This is not an unauthenticated takeover issue, but it can expose internal content and secrets.
Executive priority
Prioritize remediation for WordPress sites with multiple or semi-trusted content users. For single-admin sites, urgency is lower but updating remains recommended. Treat this as a data exposure and content integrity risk, especially where Elementor widgets store operational settings or credentials in post metadata.
Technical view
The clone handler for the ha_duplicate_thing admin action checks only the general edit_posts capability. It does not perform object-level authorization for the supplied post_id. A nonce tied to the generic action can be reused against another post_id, enabling IDOR-based cloning into an attacker-owned draft. CVSS is 5.4, with low privileges required and low confidentiality and integrity impact.
Likely exposure
Sites are exposed if they run Happy Addons for Elementor version 3.21.0 or earlier and allow untrusted Contributor, Author, Editor, or Administrator accounts. Risk is higher on multi-author, agency, membership, education, or customer-managed WordPress sites.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Abuse requires a valid authenticated WordPress account with Contributor-level permissions or higher. The main impact is unauthorized copying of existing post, page, or custom post content and associated metadata into a draft controlled by the attacker.
Researcher notes
Evidence points to CWE-639 object authorization failure in clone-handler.php. The cited code locations and WordPress Trac changeset support the issue and remediation direction, but the provided bundle does not include a detailed vendor advisory naming the exact fixed release. Avoid assuming exploit-in-the-wild status.
Mitigation direction
- Update Happy Addons for Elementor to a version newer than 3.21.0 when available.
- Review vendor and WordPress plugin guidance for the confirmed fixed release.
- Limit Contributor-level access to trusted users until remediation is complete.
- Audit duplicated drafts and unexpected content owned by low-privileged users.
- Rotate exposed API tokens if sensitive metadata may have been copied.
Validation and detection
- Inventory WordPress sites using Happy Addons for Elementor.
- Confirm plugin version; flag 3.21.0 and earlier as affected.
- Review user accounts with Contributor or higher roles.
- Inspect recent drafts duplicated from sensitive pages or custom post types.
- Check vendor advisory and plugin changelog for fixed-version confirmation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCVE-2026-2917 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/9234b1ce-032f-487d-b60a-f80c78373238?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/happy-elementor-addons/tags/3.20.7/classes/clone-handler.php#L21CVE reference
- https://plugins.trac.wordpress.org/browser/happy-elementor-addons/trunk/classes/clone-handler.php#L21CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=3475242%40happy-elementor-addons%2Ftrunk&old=3463375%40happy-elementor-addons%2Ftrunk&sfp_email=&sfph_mail=CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
