CVE-2024-9502
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 · uneditedThe Master Addons – Elementor Addons with White Label, Free Widgets, Hover Effects, Conditions, & Animations plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Tooltip module in all versions up to, and including, 2.0.6.7 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 confidenceThe Master Addons plugin's Tooltip module in versions up to 2.0.6.7 fails to properly sanitize user-supplied attributes during input and escape them during output, allowing authenticated contributors+ to inject persistent malicious JavaScript via the Tooltip settings that executes 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< 2.0.6.8CVSS 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 Master Addons plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Master Addons' or check the plugin files in /wp-content/plugins/master-addons/ for the main PHP file to identify the installed versionAffected if The Master Addons plugin is installed and active
-
Determine the installed versionCheck the plugin version in the Plugins list or read the version number from the plugin's main PHP file header (e.g., master-addons.php)Affected if The installed version is lower than 2.0.6.8
-
Confirm Tooltip module is in useReview pages, posts, or Elementor templates for any Tooltip elements added via the Master Addons Tooltip widget/module. Check custom post types or widget areas where tooltips may have been placedAffected if Any Tooltip elements created with Master Addons exist on the site and the installed version is below 2.0.6.8
-
Check for contributor+ user accountsReview WordPress user roles under Users > All Users to identify accounts with Contributor, Author, Editor, or Administrator roles who could potentially create or modify Tooltip contentAffected if Users with Contributor-level access or higher exist on the site and the Tooltip module is in use with a vulnerable version
You are affected if Master Addons version is below 2.0.6.8, the Tooltip module is actively used on your site, and contributor+ users exist who could inject malicious script through Tooltip settings.
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 · scoped2.0.6.8
Update the Master Addons plugin to version 2.0.6.8 or later, which includes proper input sanitization and output escaping for the Tooltip module attributes.
Master Addons version 2.0.6.8
- Update the Master Addons plugin to version 2.0.6.8 or later through WordPress admin > Plugins > Updates, or reinstall the plugin from the WordPress repository
- Verify the update was successfully applied by checking the plugin version in WordPress admin > Plugins
- Test the Tooltip module functionality to confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9502 — 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-9502 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