Enter AddonsWordPress extension · Themelooks
CVE-2024-37263
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 (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.
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 XSS vulnerability in Enter Addons plugin allows malicious JavaScript to be injected through user input fields that are not properly sanitized before being rendered in web pages. The vulnerability exists in versions up to 2.1.6 and could allow authenticated attackers to execute arbitrary scripts in the context of other users' browsers.
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
< 2.1.7CVSS 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.
-
Locate the Enter Addons plugin installationCheck your WordPress installation's wp-content/plugins/ directory for a folder named 'enter-addons' or look for the plugin in the WordPress admin under Plugins > Installed Plugins.Affected if The Enter Addons plugin is found in the plugins directory.
-
Identify the installed versionOpen the main plugin file (usually enter-addons.php) in a text editor and locate the 'Version' header in the plugin comment block, or view the version via WordPress admin plugins list.Affected if The version listed is below 2.1.7 (e.g., 2.1.6, 2.1.5, etc.).
-
Verify plugin is activeLog in to WordPress admin and check if Enter Addons appears in the active plugins list, or query the wp_options table for the active_plugins option.Affected if The plugin is installed and active on the site.
-
Identify user input pointsReview the Enter Addons settings and any frontend forms or input fields created by the plugin (such as contact forms, search widgets, or custom input elements).Affected if The plugin provides any user-facing input fields where content can be submitted and stored.
-
Inspect stored content for malicious scriptsSearch the wp_posts and wp_postmeta database tables for any entries containing script tags, javascript:, or on* event handlers (onclick, onerror, etc.) that may have been injected through Enter Addons input fields.Affected if Suspicious script tags or event handlers are found in stored database content.
You are affected if Enter Addons version is below 2.1.7 AND the plugin is active AND it exposes user input fields that accept and store content.
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.1.7
Update to the latest version of Enter Addons when available, or implement proper input sanitization and output encoding on all user-supplied data before rendering in HTML contexts.
Enter Addons version 2.1.7
- Create a full backup of your WordPress site (database and files) before updating
- Navigate to WordPress Admin > Plugins > Installed Plugins
- Find 'Enter Addons' in the plugin list
- Click 'Update now' if an update is available, or manually upload version 2.1.7 of Enter Addons
- Verify the plugin version shows 2.1.7 after updating
- Clear any site caching mechanisms (plugin cache, CDN cache, server-side cache)
- Test that the site functions correctly after the update
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
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37263 — 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-37263 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