CVE-2024-47392
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 ('Cross-site Scripting') vulnerability in bdthemes Element Pack Elementor Addons bdthemes-element-pack-lite allows Stored XSS.This issue affects Element Pack Elementor Addons: from n/a through <= 5.7.5.
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 confidenceA stored XSS vulnerability exists in the bdthemes Element Pack Elementor Addons WordPress plugin (versions <= 5.7.5) where user-supplied input is not properly sanitized before being rendered in web pages, allowing authenticated attackers to inject malicious JavaScript that executes in the browsers of users viewing affected pages.
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< 5.7.6CVSS 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.
-
Verify the plugin is installedNavigate to WordPress Admin > Plugins or inspect the /wp-content/plugins/ directory for 'bdthemes-element-pack-lite' or 'bdthemes-element-pack' folder. Alternatively, run: wp plugin list --name='element-pack-lite' via WP-CLIAffected if The plugin folder 'bdthemes-element-pack-lite' or 'bdthemes-element-pack' exists in the plugins directory
-
Check installed plugin versionIn WordPress Admin > Plugins, find 'Element Pack Lite' or 'Element Pack' and read the version number from the plugin details. Or inspect the main plugin file header in /wp-content/plugins/bdthemes-element-pack-lite/ for 'Version:' fieldAffected if The displayed version is 5.7.5 or lower (any version before 5.7.6)
-
Confirm authentication requirement for exploitationNote that this is an authenticated stored XSS - the attacker needs at least Contributor-level access to inject the payload. Review user roles with access to the plugin's form/contact/booking widgets where input is capturedAffected if The site allows untrusted users (below Administrator) to access or create content using Element Pack widgets
-
Identify usage of input-capturing widgetsReview pages/posts using Element Pack widgets that accept user input, such as contact forms, booking forms, registration fields, or any widget that saves and displays user-submitted data on the frontendAffected if Element Pack widgets that store and display user input are published on live pages
You are affected if the bdthemes Element Pack plugin version is 5.7.5 or lower AND the site has non-administrator users with access to create or edit content using Element Pack widgets that capture and display user input.
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 · scoped5.7.6
Update to the patched version of bdthemes-element-pack-lite when released; if no update is available, implement WAF rules to filter XSS attack vectors and restrict admin-level access to limit exposure.
5.7.6
- Log in to your WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'Element Pack Elementor Addons' (bdthemes-element-pack-lite) in the plugin list
- If an update is available, click 'Update Now' to upgrade to version 5.7.6 or later
- After updating, verify the plugin version shows 5.7.6 or higher under Plugins > Installed Plugins
- Clear any site caches (if using caching plugins) to ensure the patched version is served
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47392 — 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-47392 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