dbcve.org
Enter AddonsWordPress extension · Themelooks

CVE-2024-7611

MEDIUM · 5.4 CVSS v3.1 Published 2024-09-06
Fix available
A fix is available. Upgrade to after 2.1.9 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
The Enter Addons – Ultimate Template Builder for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'tag' attribute of the Events Card widget in all versions up to, and including, 2.1.8 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 confidence

The Enter Addons plugin for WordPress contains a stored XSS vulnerability in the Events Card widget where the 'tag' attribute fails to properly sanitize and escape user input. An authenticated attacker with contributor-level access or higher can inject malicious JavaScript code through this attribute, which then executes in the browsers of any user viewing the affected pages.

MitigationUpdate the Enter Addons plugin to version 2.1.9 or later which contains the patched version. Until patched, review existing pages using the Events Card widget and consider limiting contributor-level access to untrusted users.

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
Enter AddonsWordPress extension
Affected:<= 2.1.9

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 Enter Addons plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Enter Addons' by Themelooks. Note the installed version number displayed next to the plugin name.
    Affected if The plugin is not installed or is not present in the WordPress site.
  2. Compare installed version to affected range
    Check the version number you recorded. The affected versions are Themelooks Enter Addons <= 2.1.9. If your version is 2.1.9 or lower, the vulnerability exists.
    Affected if Installed version is 2.1.9 or lower.
  3. Identify usage of the Events Card widget
    Review your WordPress pages, posts, or widget areas where the Enter Addons Events Card widget has been added. Check page builders or widget sections where this specific widget type is configured.
    Affected if The Events Card widget from Enter Addons is actively used on any published page or post.
  4. Audit contributor-level user accounts
    In WordPress admin, go to Users > All Users and review accounts with the 'Contributor' role or higher (Author, Editor, Administrator). Identify any accounts that are untrusted or belong to users who should not have content publishing capabilities.
    Affected if There are contributor-level or higher users who should not have publishing permissions, as the vulnerability requires authenticated contributor access to exploit.

A site is affected if it has Enter Addons plugin version 2.1.9 or lower AND uses the Events Card widget AND has untrusted users with contributor-level access or higher.

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 a release after 2.1.9
Interim mitigation

Update the Enter Addons plugin to version 2.1.9 or later which contains the patched version. Until patched, review existing pages using the Events Card widget and consider limiting contributor-level access to untrusted users.

Recommended fix High confidence

Enter Addons version 2.1.9

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Enter Addons – Ultimate Template Builder for Elementor'
  4. Check if the current version is 2.1.9 or lower
  5. If vulnerable, click 'Update Now' to upgrade to version 2.1.9
  6. Verify the update completed successfully
  7. Confirm the plugin version is now 2.1.9

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

Fix this in Enter Addons Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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