dbcve.org
Mas ElementorWordPress extension · Madrasthemes

CVE-2024-49233

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-18
Fix available
A fix is available. Upgrade to 1.1.7 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in MadrasThemes MAS Elementor mas-addons-for-elementor allows DOM-Based XSS.This issue affects MAS Elementor: from n/a through <= 1.1.6.

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 · moderate confidence

DOM-based Cross-site Scripting (XSS) vulnerability in the MAS Elementor WordPress plugin allows attackers to inject malicious JavaScript through unsanitized user input that gets rendered directly into the page DOM. This client-side vulnerability executes in victim's browsers when they visit crafted pages, potentially leading to session hijacking or credential theft.

MitigationUpdate to the latest version of MAS Elementor if a patch is available; otherwise, implement proper output encoding when the plugin renders user-supplied data into HTML/JavaScript and consider adding Content-Security-Policy headers to mitigate XSS execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mas ElementorWordPress extension
Affected:< 1.1.7

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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. Confirm MAS Elementor plugin is installed
    Navigate to WordPress admin > Plugins or check the /wp-content/plugins/mas-elementor/ directory via file manager/SSH. Also check if the plugin appears in the Elementor > Mas Elements menu.
    Affected if The plugin directory mas-elementor exists in the plugins folder and is listed in the WordPress admin plugins page.
  2. Identify the installed plugin version
    Open the main plugin file at /wp-content/plugins/mas-elementor/mas-elementor.php and look for the 'Version:' header in the plugin comment block. Alternatively, use WP-CLI: wp plugin list --name=mas-elementor --format=table
    Affected if The version number shown is lower than 1.1.7 (for example: 1.1.6, 1.1.5, 1.0.x, etc.)
  3. Verify the plugin is active
    In WordPress admin > Plugins, confirm Mas Elementor shows as 'Active'. Or via WP-CLI: wp plugin status mas-elementor
    Affected if The plugin status reports as 'Active' or 'Enabled'.
  4. Confirm plugin is rendering dynamic content
    Review pages built with Elementor that use Mas Elementor widgets. Check if any Mas Elementor widgets accept and display user-supplied text fields, custom HTML, or dynamic content sources.
    Affected if Any Mas Elementor widget is actively displaying content that could include unsanitized user input on the frontend.

Your environment is affected if MAS Elementor plugin is installed, active, and running version 1.1.6 or lower while displaying content through the plugin's widgets.

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
Upgrade available Upgrade to 1.1.7 or later
Fixed in 1.1.7
Interim mitigation

Update to the latest version of MAS Elementor if a patch is available; otherwise, implement proper output encoding when the plugin renders user-supplied data into HTML/JavaScript and consider adding Content-Security-Policy headers to mitigate XSS execution.

Recommended fix High confidence

MAS Elementor version 1.1.7

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find 'MAS Elementor' (mas-addons-for-elementor) in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.1.7
  5. 5. Alternatively, download MAS Elementor version 1.1.7 from the WordPress plugin repository or MadrasThemes
  6. 6. Deactivate and delete the current version, then upload and install version 1.1.7
  7. 7. After upgrade, verify the plugin is running at version 1.1.7 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mas Elementor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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