dbcve.org
Better Elementor AddonsWordPress extension · Kitforest

CVE-2024-30423

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-29
Fix available
A fix is available. Upgrade to 1.3.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 ('Cross-site Scripting') vulnerability in BetterAddons Better Elementor Addons allows Stored XSS.This issue affects Better Elementor Addons: from n/a through 1.3.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 Cross-site Scripting (XSS) vulnerability exists in Better Elementor Addons plugin versions through 1.3.7. The plugin fails to properly sanitize user-supplied input before rendering it in web pages, allowing authenticated attackers to inject malicious JavaScript code that executes when other users view the affected content.

MitigationUpdate Better Elementor Addons to the latest version that includes proper input sanitization and output encoding. Review and validate all user inputs across plugin components.

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
Better Elementor AddonsWordPress extension
Affected:< 1.3.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 if Better Elementor Addons plugin is installed
    Log in to WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'Kitforest Better Elementor Addons' or 'Better Elementor Addons' in the list.
    Affected if The plugin is present in the WordPress installation.
  2. Determine the installed plugin version
    In the Plugins list, click on the plugin name or view details to find the version number displayed under the plugin title.
    Affected if The version number is less than 1.3.8 (for example, 1.3.7, 1.3.6, etc.).
  3. Identify if user input fields exist in the plugin
    Navigate to the plugin settings or any public-facing Elementor widgets provided by this plugin. Look for input fields where users can submit text content (such as custom widgets, content blocks, or form elements).
    Affected if The plugin provides any user-facing input fields where content is stored and displayed back on pages.
  4. Inspect page source for injected scripts
    View the source code of pages using the plugin's widgets. Look for <script> tags, javascript: URIs, or event handlers (onclick, onerror, onload) in attributes that may have been injected via the plugin's input fields.
    Affected if Unexpected JavaScript code appears in HTML attributes, content areas, or script tags that were not intentionally added by an administrator.
  5. Check database for suspicious content
    If database access is available, inspect the tables where plugin data is stored (typically wp_posts, wp_postmeta, or custom tables). Look for encoded or obfuscated content containing <script, javascript:, or event handler attributes.
    Affected if The database contains unexpected script tags or event handlers in fields associated with the plugin.

A user is affected if the Kitforest Better Elementor Addons plugin version is below 1.3.8 AND the plugin is actively used with user input capabilities enabled on the site.

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 1.3.8 or later
Fixed in 1.3.8
Interim mitigation

Update Better Elementor Addons to the latest version that includes proper input sanitization and output encoding. Review and validate all user inputs across plugin components.

Recommended fix High confidence

Better Elementor Addons version 1.3.8 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Better Elementor Addons' in the plugin list
  4. Check if the current version is below 1.3.8
  5. If vulnerable, click 'Update Now' to update to the latest version
  6. Alternatively, download version 1.3.8 or later from the WordPress plugin repository or BetterAddons official source
  7. After updating, verify the version number reflects 1.3.8 or higher

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

Fix this in Better Elementor Addons Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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