Mega ElementsWordPress extension · Kraftplugins
CVE-2024-32575
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 Kraftplugins Mega Elements allows Stored XSS.This issue affects Mega Elements: from n/a through 1.1.9.
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 WordPress plugin allows authenticated attackers to inject malicious JavaScript through unsanitized user input that gets stored in the database and executed when other users view affected pages.
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.0CVSS 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 installedCheck your WordPress plugins directory or admin panel for the 'Mega Elements' or 'Kraftplugins Mega Elements' pluginAffected if Plugin is present in the installation
-
Identify installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find the version number listed for Mega Elements; alternatively, check the plugin header in the main plugin fileAffected if Version is lower than 1.2.0 or version number cannot be determined (indicating outdated release)
-
Confirm plugin is activeIn WordPress admin Plugins page, verify Mega Elements shows as 'Active'Affected if Plugin is both installed and active with version below 1.2.0
Your environment is affected if the Mega Elements plugin is installed, active, and running a version lower than 1.2.0, enabling stored XSS via unsanitized user input in plugin features.
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.0
Update Mega Elements to the latest patched version; if no update exists, disable the plugin until a fix is available. Implement proper input sanitization and output escaping on all user-supplied data before rendering.
Mega Elements version 1.2.0
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Find the Mega Elements plugin in the list
- 4. If an update is available, click 'Update Now' to upgrade to version 1.2.0
- 5. Alternatively, download Mega Elements version 1.2.0 from the WordPress plugin repository or Kraftplugins
- 6. Deactivate and delete the current version, then upload and install version 1.2.0
- 7. After updating, verify the plugin is functioning correctly on the website
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
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-32575 — 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-32575 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