Events Addon For ElementorWordPress extension · Nicheaddons
CVE-2024-49264
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 nicheaddons Events Addon for Elementor events-addon-for-elementor allows Stored XSS.This issue affects Events Addon for Elementor: from n/a through <= 2.2.0.
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 nicheaddons Events Addon for Elementor plugin allows attackers to inject malicious JavaScript code through event input fields that are not properly sanitized before being stored and rendered in web pages. When users view affected event pages, the injected script executes in their browsers, potentially stealing session cookies or performing actions on behalf of the victim.
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
Events Addon For ElementorWordPress extension
< 2.2.1CVSS 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 plugin is installedCheck your WordPress installation for the Nicheaddons Events Addon For Elementor plugin. This can be done via the WordPress admin dashboard under Plugins, or by checking for the plugin directory in your wp-content/plugins folder.Affected if The plugin is present in the installation
-
Check installed versionLocate the plugin version number. In WordPress admin, go to Plugins > Installed Plugins and find the version listed for Nicheaddons Events Addon For Elementor. Alternatively, check the main plugin file for a version constant or header.Affected if The installed version is lower than 2.2.1
-
Confirm event functionality is in useCheck if any events have been created using the plugin. In the WordPress admin, look for an Events post type or custom post type added by the plugin. This could appear as a dedicated Events menu item.Affected if Events have been created and stored in the database
-
Identify exposed event input fieldsVisit the frontend of your website where events are displayed. Locate input fields where event data is entered (such as event title, description, date fields, location fields, or custom event metadata). These are the vectors where unsanitized input could be stored.Affected if Event input fields are accessible and user-supplied data can be entered and saved
Your environment is affected if the Nicheaddons Events Addon For Elementor plugin is installed with a version lower than 2.2.1 and event input fields are being used to store user-supplied data.
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.2.1
Update Events Addon for Elementor to the latest patched version. Until an update is available, implement output encoding for all event data displayed on pages and consider input validation/sanitization using WordPress sanitization functions (such as sanitize_text_field, esc_html, esc_attr) at all points where user-supplied event data is processed and displayed.
2.2.1
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate 'Events Addon For Elementor' by nicheaddons
- Verify current version is <= 2.2.0
- Click 'Update now' or 'Update' on the plugin card
- Wait for update to complete
- Verify the plugin now shows version 2.2.1 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Events Addon For Elementor
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49264 — 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-49264 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