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

CVE-2026-2918

MEDIUM · 6.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 →
70/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_condition_update` AJAX action. This is due to the `validate_reqeust()` method using `current_user_can('edit_posts', $template_id)` instead of `current_user_can('edit_post', $template_id)` — failing to perform object-level authorization. Additionally, the `ha_get_current_condition` AJAX action lacks a capability check. This makes it possible for authenticated attackers, with Contributor-level access and above, to modify the display conditions of any published `ha_library` template. Because the `cond_to_html()` renderer outputs condition values into HTML attributes without proper escaping (using string concatenation instead of `esc_attr()`), an attacker can inject event handler attributes (e.g., `onmouseover`) that execute JavaScript when an administrator views the Template Conditions panel, resulting in Stored Cross-Site Scripting.

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 plugin for WordPress has three chained vulnerabilities: (1) IDOR in `ha_condition_update` due to using `current_user_can('edit_posts', $template_id)` instead of object-level `edit_post`, (2) missing capability check on `ha_get_current_condition`, and (3) stored XSS in `cond_to_html()` where condition values are concatenated into HTML attributes without `esc_attr()`, allowing `onmouseover` event handler injection that executes when admins view the Template Conditions panel.

MitigationUpdate to version 3.21.1 or later which corrects the capability checks and adds proper escaping with `esc_attr()` for all condition values rendered into HTML attributes.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Check if Happy Addons plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Happy Addons' or check the file /wp-content/plugins/happy-addons-for-elementor/
    Affected if Plugin is installed and active
  2. Determine installed Happy Addons version
    In WordPress admin Plugins list, find Happy Addons and note the version number displayed, or check the version in the plugin's main PHP file header
    Affected if Version is lower than 3.21.1
  3. Confirm Template Conditions feature is in use
    Check if any page/post template has conditions configured in Elementor with Happy Addons, or look for database entries in wp_postmeta where meta_key contains 'ha_condition'
    Affected if Template conditions have been created and saved in the database
  4. Verify vulnerability is exploitable
    The IDOR and missing capability checks require the Template Conditions feature to be enabled; the stored XSS triggers when an admin visits the Template Conditions panel in the WordPress admin
    Affected if Happy Addons version is below 3.21.1 AND Template Conditions feature has been used to add conditions to any template

A user is affected if they have Happy Addons for WordPress installed with a version lower than 3.21.1 and have created at least one template condition, as the chained vulnerabilities (IDOR, missing capability check, and stored XSS) require the Template Conditions feature to be active.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 3.21.1 or later which corrects the capability checks and adds proper escaping with `esc_attr()` for all condition values rendered into HTML attributes.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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