Premium Addons For ElementorWordPress extension · Leap13
CVE-2023-34012
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in Premium Addons for Elementor Premium Addons PRO plugin <= 2.8.24 versions.
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 reflected cross-site scripting (XSS) vulnerability exists in the Premium Addons PRO plugin for Elementor affecting versions 2.8.24 and below. The flaw allows unauthenticated attackers to inject malicious JavaScript through unsanitized user input, which gets reflected back in the HTTP response. This could enable session hijacking, credential theft, or defacement when users click a crafted link.
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
Premium Addons For ElementorWordPress extension
<= 2.8.24CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Locate the Premium Addons PRO plugin filesCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'premium-addons-for-elementor' or similar Leap13 Premium Addons plugin directoriesAffected if The plugin folder exists on the server
-
Identify the installed version numberOpen the main plugin PHP file (typically premium-addons-for-elementor.php) and locate the 'Version' header in the plugin comment block, or check the plugin metadata via WordPress admin under Plugins > Installed PluginsAffected if The version displayed is 2.8.24 or lower
-
Verify the plugin is activeCheck the WordPress database wp_options table for option_name 'active_plugins', or view the Plugins page in WordPress admin to confirm the plugin statusAffected if The plugin appears in the list of active plugins
-
Confirm exposure to unauthenticated requestsSince this is a reflected XSS affecting unauthenticated users, verify the site frontend is accessible and the plugin is rendering any of its widgets or shortcodes on public pagesAffected if The plugin is active and accessible to visitors without authentication
If Premium Addons PRO for Elementor is installed, active, and the installed version is 2.8.24 or lower, the environment is affected by this reflected XSS vulnerability.
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.
From vendor dataUpdate Premium Addons PRO to a version higher than 2.8.24, or remove the plugin if no update is available. If immediate patching is not feasible, implement Web Application Firewall (WAF) rules to block XSS attack patterns and warn users against clicking untrusted links.
Fix this in Premium Addons For Elementor
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34012 — 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-2023-34012 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