dbcve.org
Mega ElementsWordPress extension · Kraftplugins

CVE-2024-37466

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-21
Fix available
A fix is available. Upgrade to 1.2.3 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 (XSS or 'Cross-site Scripting') vulnerability in Kraftplugins Mega Elements.This issue affects Mega Elements: from n/a through 1.2.2.

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

A stored Cross-Site Scripting (XSS) vulnerability exists in the Mega Elements WordPress plugin up to version 1.2.2. The vulnerability allows authenticated users with low-level privileges ( contributor or above) to inject malicious JavaScript code through plugin settings that are not properly sanitized before being rendered in the page, leading to script execution when other users view the affected content.

MitigationUpdate Mega Elements to the latest version which includes proper input sanitization and output escaping. If no update is available, implement output escaping at theme/plugin level or deploy a Web Application Firewall (WAF) as an interim control.

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
Affected:< 1.2.3

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. Verify Mega Elements plugin installation and version
    Navigate to WordPress admin panel > Plugins > Installed Plugins. Locate 'Mega Elements' or 'Kraftplugins Mega Elements' and note the version number displayed. Alternatively, inspect the plugin main file header for the 'Version' field.
    Affected if The installed version is below 1.2.3 (for example, 1.2.2, 1.2.1, 1.0.0, etc.)
  2. Confirm plugin is active
    Check the status column in the WordPress plugins list. The plugin must be active for the stored XSS to be exploitable.
    Affected if Mega Elements plugin is active and the version is below 1.2.3
  3. Inspect plugin settings for injected scripts
    Navigate to the Mega Elements plugin settings page in wp-admin. Look for any text input fields, textarea fields, or configuration options that may contain unexpected script tags, iframe tags, or javascript: URIs. Check both saved settings and any preview/output areas.
    Affected if Any plugin setting field contains raw HTML, script tags, or JavaScript event handlers (onclick, onerror, etc.) without proper escaping
  4. Check database for suspicious stored values
    Query the wp_options table (or equivalent) for option_name values containing 'mega_elements' or 'kraftplugins'. Examine the option_value for any encoded or raw JavaScript code, base64 payloads, or suspicious URLs.
    Affected if Database entries for Mega Elements settings contain unescaped HTML tags, script elements, or event handler attributes

Your environment is affected if the Mega Elements plugin is installed, active, and running a version lower than 1.2.3, or if malicious scripts are found stored in the plugin settings.

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.2.3 or later
Fixed in 1.2.3
Interim mitigation

Update Mega Elements to the latest version which includes proper input sanitization and output escaping. If no update is available, implement output escaping at theme/plugin level or deploy a Web Application Firewall (WAF) as an interim control.

Recommended fix Moderate confidence

1.2.3

  1. Backup your WordPress database and files before proceeding
  2. Log in to your WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Locate the Mega Elements plugin in the list
  5. Check if version 1.2.3 is available as an update
  6. If an update is available, click 'Update Now' to install version 1.2.3
  7. After the update completes, verify the installed version shows 1.2.3
  8. Test the plugin functionality to ensure the update did not break existing features

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

Fix this in Mega Elements Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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