Is Enter Addons safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (2.3.4). As of 2026-11-04. 10 issues are on record for older versions; version 2.3.3 or newer fixes all of them that state a fix. Keep Enter Addons on the latest version (2.3.4) and remove it if you do not use it.

Which versions of Enter Addons are vulnerable?

Known issues on record (newest first): Cross-site request forgery (CSRF) (2.3.2 and older, fixed in 2.3.3); Stored cross-site scripting (XSS) (2.2.7 and older, fixed in 2.2.8); Stored cross-site scripting (XSS) (2.1.9 and older, fixed in 2.2.1); Information disclosure (2.1.9 and older, fixed in 2.2.2); Stored cross-site scripting (XSS) (2.1.8 and older, fixed in 2.1.9); Stored cross-site scripting (XSS) (2.1.8 and older, fixed in 2.2.2). The full list with sources is on this page.

What is the latest version of Enter Addons?

2.3.4, according to wordpress.org (last updated 2026-06-06). It has 1,000+ active installs.

What should I do if my Enter Addons is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update enteraddons). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · enteraddons · data as of 2026-11-04

Is Enter Addons safe? Known vulnerabilities and latest version

Latest version: 2.3.4
Last updated: 2026-06-06
Active installs: 1,000+
Known issues on record: 10
Unpatched in latest: 0
Tested up to WP: 7.0.8 · PHP 7.4+

EnterAddons | Ultimate Addons For WordPress And Elementor — by themelooks

What to do

Update to the latest version (2.3.4). Anything older than 2.3.3 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get enteraddons --field=version shows what you run; wp plugin update enteraddons updates it.

Check your version

Known vulnerabilities

10 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 4.3 CVE-2026-25014 · published 2026-02-03

Cross-site request forgery (CSRF) in Enter Addons (2.3.2 and older)

Affected: 2.3.2 and older
Fixed in: 2.3.3
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Cross-Site Request Forgery (CSRF) vulnerability in themelooks Enter Addons enteraddons allows Cross Site Request Forgery.This issue affects Enter Addons: from n/a through <= 2.3.2.

NVD CVE-2026-25014 Patchstack advisory

medium 6.4 CVE-2025-8687 · published 2025-12-13

Stored cross-site scripting (XSS) in Enter Addons (2.2.7 and older)

Affected: 2.2.7 and older
Fixed in: 2.2.8 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Enter Addons plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Countdown and Image Comparison widgets in all versions up to, and including, 2.2.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.

NVD CVE-2025-8687 Wordfence advisory Code change (fix)wordpress.org

medium 5.4 CVE-2024-56252 · published 2025-01-02

Stored cross-site scripting (XSS) in Enter Addons (2.1.9 and older)

Affected: 2.1.9 and older
Fixed in: 2.2.1
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in themelooks Enter Addons enteraddons allows Stored XSS.This issue affects Enter Addons: from n/a through <= 2.1.9.

NVD CVE-2024-56252 Patchstack advisory

medium 4.3 CVE-2024-10868 · published 2024-11-23

Information disclosure in Enter Addons (2.1.9 and older)

Affected: 2.1.9 and older
Fixed in: 2.2.2 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Enter Addons – Ultimate Template Builder for Elementor plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 2.1.9 via the Advanced Tabs widget due to insufficient restrictions on which posts can be included. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract data from private or draft posts created by Elementor that they should not have access to.

NVD CVE-2024-10868 Wordfence advisory Code change (fix)wordpress.org

medium 5.4 CVE-2024-47625 · published 2024-10-05

Stored cross-site scripting (XSS) in Enter Addons (2.1.8 and older)

Affected: 2.1.8 and older
Fixed in: 2.1.9
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

NVD CVE-2024-47625 Patchstack advisory

medium 5.4 CVE-2024-7611 · published 2024-09-06

Stored cross-site scripting (XSS) in Enter Addons (2.1.8 and older)

Affected: 2.1.8 and older
Fixed in: 2.2.2 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

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.

NVD CVE-2024-7611 Wordfence advisory Code change (fix)Plugin source

medium 5.4 CVE-2024-43225 · published 2024-08-12

Stored cross-site scripting (XSS) in Enter Addons (2.1.7 and older)

Affected: 2.1.7 and older
Fixed in: 2.2.2 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in ThemeLooks Enter Addons allows Stored XSS.This issue affects Enter Addons: from n/a through 2.1.7.

NVD CVE-2024-43225 Patchstack advisory

medium 5.4 CVE-2024-37263 · published 2024-07-22

Stored cross-site scripting (XSS) in Enter Addons (2.1.6 and older)

Affected: 2.1.6 and older
Fixed in: 2.1.7
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in ThemeLooks Enter Addons enteraddons allows Stored XSS.This issue affects Enter Addons: from n/a through 2.1.6.

NVD CVE-2024-37263 Patchstack advisory

medium 5.4 CVE-2024-3831 · published 2024-05-14

Stored cross-site scripting (XSS) in Enter Addons (2.1.5 and older)

Affected: 2.1.5 and older
Fixed in: 2.2.2 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

The Enter Addons – Ultimate Template Builder for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Heading widget in all versions up to, and including, 2.1.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor access or above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

NVD CVE-2024-3831 Wordfence advisory Code change (fix)wordpress.org

medium 5.4 CVE-2024-3680 · published 2024-05-14

Stored cross-site scripting (XSS) in Enter Addons (2.1.5 and older)

Affected: 2.1.5 and older
Fixed in: 2.2.2 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

The Enter Addons – Ultimate Template Builder for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Animation Title widget's img tag in all versions up to, and including, 2.1.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor access and higher, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

NVD CVE-2024-3680 Wordfence advisory Code change (fix)wordpress.org

Recent activity

2026-06-06 — latest release on wordpress.org (2.3.4).
2026-02-03 — Cross-site request forgery (CSRF) disclosed (CVE-2026-25014), fixed in 2.3.3.
2025-12-13 — Stored cross-site scripting (XSS) disclosed (CVE-2025-8687), fixed in 2.2.8.
2025-01-02 — Stored cross-site scripting (XSS) disclosed (CVE-2024-56252), fixed in 2.2.1.

Free. We check the CVE feeds every day and email you only when a new issue for Enter Addons (enteraddons) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site scripting (XSS) (8) · Cross-site request forgery (CSRF) (1) · Sensitive data exposure (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/enteraddons (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/enteraddons"><img src="https://laskyr.com/plugins/enteraddons/badge.svg" alt="Enter Addons vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is Enter Addons safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (2.3.4)

What to do

Check your version

Known vulnerabilities

Cross-site request forgery (CSRF) in Enter Addons (2.3.2 and older)

Stored cross-site scripting (XSS) in Enter Addons (2.2.7 and older)

Stored cross-site scripting (XSS) in Enter Addons (2.1.9 and older)

Information disclosure in Enter Addons (2.1.9 and older)

Stored cross-site scripting (XSS) in Enter Addons (2.1.8 and older)

Stored cross-site scripting (XSS) in Enter Addons (2.1.8 and older)

Stored cross-site scripting (XSS) in Enter Addons (2.1.7 and older)

Stored cross-site scripting (XSS) in Enter Addons (2.1.6 and older)

Stored cross-site scripting (XSS) in Enter Addons (2.1.5 and older)

Stored cross-site scripting (XSS) in Enter Addons (2.1.5 and older)

Recent activity

Get an email when Enter Addons has a new vulnerability

Browse vulnerabilities

Where this data comes from