dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-9281

MEDIUM · 6.4 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 →
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 Master Addons For Elementor – Widgets, Extensions, Theme Builder, Popup Builder & Template Kits plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'jtlma_custom_js' Page Setting (Custom JS Extension) in all versions up to, and including, 3.1.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The unfiltered_html capability check is only enforced during Elementor control registration (UI rendering) and not during the save process, enabling Author-level users to inject the jtlma_custom_js setting directly via a crafted POST request to admin-ajax.php?action=elementor_ajax, bypassing the UI-level restriction entirely.

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 Master Addons For Elementor plugin fails to properly sanitize and escape the jtlma_custom_js parameter during the save process. Although the UI enforces unfiltered_html capability checks during control registration, this restriction is absent when data is saved via admin-ajax.php?action=elementor_ajax, allowing author-level users to inject malicious JavaScript that executes when pages containing the Custom JS Extension are accessed.

MitigationUpdate the plugin to a version beyond 3.1.0 when available, and implement proper input sanitization (sanitize_text_field or similar) and output escaping (wp_json_encode or similar) for the jtlma_custom_js setting during the save process.

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. Verify Master Addons For Elementor is installed
    Check the WordPress plugin directory or wp-admin Plugins page for 'Master Addons For Elementor'. Alternatively, inspect the plugin main file header in wp-content/plugins/master-addons-for-elementor/ for the Version field.
    Affected if The plugin is installed and the version is 3.1.0 or lower
  2. Compare installed version to the affected range
    Locate the plugin version number from the plugin header or WordPress admin plugin list. Compare it to the fixed version threshold of 3.1.0 - versions 3.1.0 and below are vulnerable.
    Affected if Installed version is 3.1.0 or lower, or version cannot be determined (treat as vulnerable)
  3. Confirm jtlma_custom_js Page Setting exists
    Navigate to a page edit screen in Elementor, open Page Settings, and look for a 'Custom JS' or 'jtlma_custom_js' field under the Master Addons section. Alternatively, check if the setting is stored in postmeta with meta_key containing 'jtlma_custom_js'.
    Affected if The jtlma_custom_js setting field is present and accessible in the Page Settings UI
  4. Identify Author-level user accounts
    In wp-admin, go to Users and review roles. Authors have the 'edit_posts' capability but NOT 'unfiltered_html'. Check which users have the Author role assigned.
    Affected if There are user accounts with the Author role in the WordPress installation
  5. Test admin-ajax.php capability enforcement (optional, requires testing)
    As an Author-level user, attempt a POST request to admin-ajax.php with action=jtlma_save_page_settings and a jtlma_custom_js parameter containing test JavaScript. Observe if the request succeeds without returning a capability error.
    Affected if The request succeeds and accepts JavaScript input without validating unfiltered_html capability

If the plugin is installed at version 3.1.0 or lower, the jtlma_custom_js setting exists, and Author-level users are present, the environment is vulnerable to this privilege escalation.

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 plugin to a version beyond 3.1.0 when available, and implement proper input sanitization (sanitize_text_field or similar) and output escaping (wp_json_encode or similar) for the jtlma_custom_js setting during the save process.

Recommended fix Moderate confidence

Latest version available on WordPress plugin repository (after 3.1.0)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Master Addons For Elementor' in the plugin list
  4. Check if the current version is 3.1.0 or earlier
  5. If vulnerable, click 'Update Now' or manually download the latest version from wordpress.org/plugins/master-addons-for-elementor/
  6. After updating, verify the version number reflects the latest release (should be newer than 3.1.0)

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