dbcve.org
Better Elementor AddonsWordPress extension · Kitforest

CVE-2024-34432

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 1.4.5 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 better-elementor-addons allows Stored XSS.This issue affects Better Elementor Addons: from n/a through 1.4.4.

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 · high confidence

A Stored Cross-Site Scripting (XSS) vulnerability exists in Better Elementor Addons plugin versions up to 1.4.4. An authenticated attacker with low privileges can inject malicious JavaScript code into plugin settings or content fields, which is then stored in the database and executed when other users (including administrators) view the affected pages in the WordPress dashboard or frontend.

MitigationUpgrade to a patched version of Better Elementor Addons (if available) or implement output sanitization/escaping on all user-supplied input fields within the plugin to prevent script execution.

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

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 plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Kitforest Better Elementor Addons'. Check the version number displayed under the plugin name. Alternatively, inspect the plugin header in /wp-content/plugins/kitforest-better-elementor-addons/ or the main plugin PHP file for the 'Version' tag.
    Affected if The installed version is 1.4.4 or lower (any version below 1.4.5)
  2. Confirm plugin is active
    Check that the Kitforest Better Elementor Addons plugin is currently activated in the WordPress site. In the WordPress admin, go to Plugins > Installed Plugins and verify the plugin shows 'Active' status.
    Affected if The plugin is active and vulnerable versions are installed
  3. Inspect database for injected scripts
    Query the WordPress database (via phpMyAdmin or wp-cli) for stored XSS payloads in plugin-related tables. Look for script tags, javascript:, or event handler attributes (onload, onerror, onclick) in fields related to plugin settings, widget content, or addon configurations. Common tables include wp_posts, wp_postmeta, and wp_options.
    Affected if Any script tags or malicious JavaScript code is found stored in plugin-related database fields
  4. Review plugin settings pages
    Navigate to the plugin settings pages in the WordPress admin dashboard (typically under Elementor > Addons or a dedicated Kitforest menu). Inspect page source or use browser developer tools to check form inputs and content display areas for unescaped output.
    Affected if User-supplied input in plugin settings fields renders without proper escaping when viewed

The environment is affected if Kitforest Better Elementor Addons version 1.4.4 or lower is installed and active, or if suspicious script tags are found stored in plugin-related database fields.

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.4.5 or later
Fixed in 1.4.5
Interim mitigation

Upgrade to a patched version of Better Elementor Addons (if available) or implement output sanitization/escaping on all user-supplied input fields within the plugin to prevent script execution.

Recommended fix High confidence

1.4.5

  1. Log in to your 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.4.5
  5. If vulnerable, navigate to Dashboard > Updates or Plugins > Add New > Upload Plugin
  6. Update Better Elementor Addons to version 1.4.5 or later
  7. Verify the update was successful by checking the plugin version

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

Fix this in Better Elementor Addons Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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 locally
dbcve dependency scanner

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