Woolentor Woocommerce Elementor Addons \+ BuilderWordPress extension · Hasthemes
CVE-2021-24262
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 · uneditedThe “WooLentor – WooCommerce Elementor Addons + Builder” WordPress Plugin before 1.8.6 has a widget that is vulnerable to stored Cross-Site Scripting (XSS) by lower-privileged users such as contributors, all via a similar method.
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 confidenceThe WooLentor WordPress plugin before version 1.8.6 contains a stored XSS vulnerability in one of its widgets. Lower-privileged users such as contributors can inject malicious JavaScript code through the widget settings, which then executes when viewed by administrators or other users accessing the affected widget.
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
Woolentor Woocommerce Elementor Addons \+ BuilderWordPress extension
< 1.8.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.
-
Check WooLentor plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate 'WooLentor - WooCommerce Elementor Addons + Builder'. The version number is displayed below the plugin name. Compare this to the affected range (versions before 1.8.6).Affected if The installed version is lower than 1.8.6
-
Identify active WooLentor widgetsReview pages, posts, and custom post types that use Elementor. In the WordPress admin, navigate to Pages or Posts and look for any content edited with Elementor that contains WooLentor widgets (such as product sliders, product grids, or other WooCommerce-related widgets).Affected if Any WooLentor widgets are present in published content
-
Inspect widget settings for injected scriptsEdit each page/post containing WooLentor widgets using Elementor. Click on each Woolentor widget and review the settings fields (particularly text inputs, URLs, or content fields). Look for suspicious patterns such as <script> tags, javascript: URLs, or event handlers like onerror, onload, onclick within the field values.Affected if Any widget settings contain raw script tags, javascript: protocols, or HTML event handler attributes
-
Review content created by lower-privileged usersIn WordPress admin, go to Users > All Users to identify users with Contributor or Author roles. Then check the content they have created (Posts > All Posts, Pages > All Pages) that may include WooLentor widgets. Inspect the widget configurations for encoded or obfuscated payloads.Affected if Lower-privileged users have created content with WooLentor widgets and those widget settings contain unexpected characters or encoded content
You are affected if the WooLentor plugin version is below 1.8.6 AND any WooLentor widget is in use, particularly if created or edited by users with Contributor or Author roles.
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 data1.8.6
Update the WooLentor plugin to version 1.8.6 or later. Review and sanitize any existing content created by lower-privileged users that may contain malicious XSS payloads.
Fix this in Woolentor Woocommerce Elementor Addons \+ Builder
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-24262 — 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-2021-24262 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