dbcve.org
Enter AddonsWordPress extension · Themelooks

CVE-2024-47625

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

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

Stored Cross-site Scripting (XSS) vulnerability in themelooks Enter Addons WordPress plugin allows attackers to inject malicious JavaScript code through unsanitized user input. The payload is stored in the database and executed when other users view affected pages, potentially leading to session hijacking, credential theft, or malicious actions performed in the context of authenticated users.

MitigationUpdate Enter Addons plugin to the latest version when available, which should include proper input sanitization and output encoding. If no patch is available, implement Web Application Firewall (WAF) rules to block XSS payloads and audit the plugin for vulnerable input fields.

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. Check Enter Addons plugin version in WordPress admin
    Navigate to WordPress admin > Plugins > Installed Plugins. Locate 'Enter Addons' by Themelooks and examine the version number displayed under the plugin name. Compare this version against 2.1.9.
    Affected if The installed version is displayed as anything less than 2.1.9 (for example, 2.1.8, 2.1.7, etc.) or if no version number is shown but the plugin appears outdated.
  2. Verify plugin files directly via filesystem
    Access the WordPress plugins directory (wp-content/plugins/) and locate the enter-addons folder. Check the main plugin file (usually enter-addons.php or index.php) for the version header comment or constant definition.
    Affected if The version string found in the plugin files reads lower than 2.1.9.
  3. Confirm plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify that Enter Addons shows 'Active' status under the plugin name.
    Affected if The plugin is active and the version is below 2.1.9.
  4. Identify exposed input fields
    Examine the WordPress pages where Enter Addons provides user-facing forms, widgets, or content creation tools. Common locations include page builders, form widgets, or custom post type interfaces that accept user-supplied text input.
    Affected if The plugin provides any input fields that accept user text and display it on the frontend without visible sanitization indicators.

You are affected if the Enter Addons plugin is active and the installed version is below 2.1.9, as this version range contains the unsanitized input fields enabling stored XSS.

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.9 or later
Fixed in 2.1.9
Interim mitigation

Update Enter Addons plugin to the latest version when available, which should include proper input sanitization and output encoding. If no patch is available, implement Web Application Firewall (WAF) rules to block XSS payloads and audit the plugin for vulnerable input fields.

Recommended fix High confidence

2.1.9

  1. Backup your WordPress site and database before making any changes
  2. Navigate to your WordPress admin dashboard
  3. Go to Plugins > Installed Plugins
  4. Find 'Enter Addons' in the plugin list
  5. Click 'Update now' if an update is available, or manually upload version 2.1.9
  6. Verify the plugin updated successfully to version 2.1.9 or higher
  7. Test the site functionality to ensure the update did not break any features
Caveat Review plugin changelog for any breaking changes before updating; test in staging environment first if possible

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 / QA1.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-47625 — 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-47625 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