Mega ElementsWordPress extension · Kraftplugins
CVE-2024-49693
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Kraft Plugins Mega Elements mega-elements-addons-for-elementor allows Stored XSS.This issue affects Mega Elements: from n/a through <= 1.2.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 confidenceStored Cross-site Scripting (XSS) vulnerability in the Mega Elements Addons for Elementor plugin allows authenticated attackers to inject malicious JavaScript code through unsanitized user inputs. This script executes when other users view pages containing the affected content.
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
Mega ElementsWordPress extension
< 1.2.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Mega Elements plugin is installedLog into WordPress admin, navigate to Plugins > Installed Plugins, and look for 'Mega Elements Addons for Elementor' or 'Kraftplugins Mega Elements' in the list of installed plugins.Affected if The plugin is not found in the installed plugins list, so the vulnerability does not apply.
-
Locate the installed version numberIn the WordPress Plugins list, find the Mega Elements plugin and note the version number displayed beneath the plugin name. Alternatively, access the plugin files via FTP or file manager and open the main plugin file (usually mega-elements-addons-for-elementor.php) to read the 'Version' header comment.Affected if The version cannot be determined from the plugin files.
-
Compare version against affected rangeCompare the installed version number to the affected range: versions prior to 1.2.7 are vulnerable. For example, 1.2.6, 1.2.5, 1.0.0, and all versions below 1.2.7 are within the affected range.Affected if The installed version is less than 1.2.7 (for example, 1.2.6 or lower).
-
Determine if Elementor page editing is accessible to authenticated usersCheck if the WordPress site has user registration enabled or has users with contributor, author, editor, or administrator roles who can create or edit pages using the Elementor page builder.Affected if Authenticated users with access to Elementor can create or edit content, allowing them to trigger the vulnerable input fields.
You are affected if the Mega Elements Addons for Elementor plugin is installed with a version number lower than 1.2.7 and your site allows authenticated users to create or edit Elementor content.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.2.7
Update to the latest version of Mega Elements if a patch is available. Otherwise, implement proper input sanitization and output encoding on all user-supplied data before rendering in web pages.
1.2.7
- 1. Back up your WordPress site before performing any plugin updates
- 2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
- 3. Locate 'Mega Elements - mega-elements-addons-for-elementor' in the plugin list
- 4. If an update is available, click 'Update Now' to update to version 1.2.7
- 5. Alternatively, go to Dashboard > Updates and select the Mega Elements plugin to update
- 6. After updating, verify the plugin version shows 1.2.7
- 7. Test the affected functionality to ensure the plugin still works correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Mega Elements
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49693 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-49693 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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