dbcve.org
Enter AddonsWordPress extension · Themelooks

CVE-2024-43225

MEDIUM · 5.4 CVSS v3.1 Published 2024-08-12
Fix available
A fix is available. Upgrade to 2.1.8 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
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.

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

A stored XSS vulnerability exists in ThemeLooks Enter Addons (versions up to 2.1.7) where user-supplied input is not properly sanitized before being stored and displayed in web pages. This allows authenticated attackers to inject malicious JavaScript that executes in browsers of users viewing the affected content.

MitigationUpdate Enter Addons to the latest version after the fix is released, or implement proper input sanitization and output encoding at all points where user input is rendered in HTML contexts.

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.8

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 is installed
    Check your WordPress installation under wp-content/plugins/enter-addons/ folder, or view the installed plugins list in WordPress admin under Plugins > Installed Plugins
    Affected if Enter Addons plugin appears in your plugins list
  2. Determine the installed version
    In WordPress admin, go to Plugins > Installed Plugins > Enter Addons and note the version number displayed, or check the main plugin PHP file for the Version header comment
    Affected if Version is 2.1.7 or lower, or any version number less than 2.1.8
  3. Confirm authentication access to Enter Addons features
    Review which user roles have access to Enter Addons settings and content creation features under the plugin menu options
    Affected if Any user role other than Administrator has permission to access Enter Addons creation or settings features
  4. Search for suspicious stored content
    Use a database query or WordPress admin to search post meta, options, and custom post types created by Enter Addons for unusual script tags, javascript: URLs, or event handler attributes in content fields
    Affected if Any stored content contains unsanitized HTML script tags or JavaScript event handlers

Your environment is affected if Enter Addons version is below 2.1.8 and authenticated users can access its content creation features, or if anomalous script-containing content already exists in your database.

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.8 or later
Fixed in 2.1.8
Interim mitigation

Update Enter Addons to the latest version after the fix is released, or implement proper input sanitization and output encoding at all points where user input is rendered in HTML contexts.

Recommended fix High confidence

Enter Addons 2.1.8

  1. 1. Backup your WordPress site before making any changes.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Locate Enter Addons in the plugin list.
  5. 5. Check if an update to version 2.1.8 or higher is available.
  6. 6. If an update is available, click 'Update Now' to install version 2.1.8.
  7. 7. If no update is shown, manually download Enter Addons version 2.1.8 or later from a trusted source (such as the official WordPress plugin repository).
  8. 8. Deactivate the current Enter Addons plugin, delete it, then upload and install the new version.

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
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
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,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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