dbcve.org
Events Addon For ElementorWordPress extension · Nicheaddons

CVE-2023-47827

HIGH · 7.5 CVSS v3.1 Published 2023-11-30
Fix available
A fix is available. Upgrade to 2.1.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Incorrect Authorization vulnerability in NicheAddons Events Addon for Elementor allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Events Addon for Elementor: from n/a through 2.1.3.

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

The NicheAddons Events Addon for Elementor plugin versions up to 2.1.3 contains an incorrect authorization vulnerability that allows users to access functionality that should be constrained by access control lists (ACLs). This is a broken access control (BAC) issue where the plugin fails to properly verify user permissions before allowing access to sensitive features or administrative functions.

MitigationUpdate to the latest version of NicheAddons Events Addon for Elementor when a patch is released. If no patch is available, audit user roles and permissions, restrict access to the plugin's admin functions, and consider disabling the plugin until a fix is available.

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

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 the NicheAddons Events Addon plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'NicheAddons Events Addon For Elementor' or check the file path wp-content/plugins/niche-addons-events for elementor
    Affected if The plugin is installed and active in the WordPress environment
  2. Determine the installed version of the plugin
    In WordPress admin, go to Plugins > Installed Plugins, find the NicheAddons Events Addon entry, and note the version number displayed. Alternatively, check the main plugin file header in wp-content/plugins/niche-addons-events-for-elementor/niche-addons-events-for-elementor.php for the Version field
    Affected if The version is 2.1.3 or lower (any version below 2.1.4)
  3. Inspect user role capabilities related to the plugin
    Use a role editor plugin or query the wp_options table for option_name containing 'user_roles' to review what capabilities are assigned to subscriber, contributor, author, editor, and administrator roles. Check if non-admin users have access to events-related capabilities that should be restricted
    Affected if Lower-privileged users (subscriber, contributor, author) have administrative or events management capabilities they should not possess
  4. Test access to plugin admin functions
    Log in as a low-privileged user (subscriber or contributor) and attempt to access the Elementor editor with the events addon. Check if they can create, edit, or delete events that should require elevated permissions
    Affected if A non-administrator user can access or modify events functionality that should be restricted to admins only

The environment is affected if the NicheAddons Events Addon For Elementor plugin version is 2.1.3 or lower AND low-privileged users can access administrative events functions that should be restricted.

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 2.1.4 or later
Fixed in 2.1.4
Interim mitigation

Update to the latest version of NicheAddons Events Addon for Elementor when a patch is released. If no patch is available, audit user roles and permissions, restrict access to the plugin's admin functions, and consider disabling the plugin until a fix is available.

Recommended fix Moderate confidence

2.1.4 or later

  1. Backup your WordPress site before performing any updates
  2. Navigate to WordPress Dashboard > Plugins
  3. Locate the Events Addon For Elementor plugin by NicheAddons
  4. Update the plugin to version 2.1.4 or later
  5. Verify the update was successful by checking the installed version
  6. Test the events functionality to ensure proper authorization controls are working correctly

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

Fix this in Events Addon For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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 locally
dbcve dependency scanner

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