CVE-2026-6287
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 ShopLentor - WooCommerce Builder for Elementor & Gutenberg plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'blockUniqId' block attribute in multiple Product Gride blocks in versions up to, and including, 3.3.8 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 confidenceThe ShopLentor WooCommerce builder plugin for WordPress versions up to 3.3.8 contains a stored XSS vulnerability in the 'blockUniqId' block attribute of Product Grid blocks. Authenticated attackers with contributor-level access can inject malicious JavaScript via insufficiently sanitized input that executes when users access affected pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify ShopLentor plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and locate ShopLentor (also known as WooLentor). Note the installed version number.
-
Compare installed version to fixed releaseCompare the installed version you found in step 1 against version 3.3.9 (the patched release). The plugin is vulnerable if your version is lower than 3.3.9.
-
Identify Product Grid block usageCheck your WordPress pages, posts, or widgets for instances of ShopLentor Product Grid blocks. This can be done by viewing page content in the block editor or inspecting the postmeta table for post_content containing 'woolentor-product-grid' or similar block references.
-
Inspect blockUniqId parameter for unescaped contentExamine the HTML source of pages containing Product Grid blocks. Look for the blockUniqId attribute value in the block markup. If you see unescaped special characters like <, >, ", or ' appearing literally in the attribute, or if you can inject script tags that execute, the XSS is present.
You are affected if ShopLentor is installed with a version below 3.3.9 AND Product Grid blocks using the blockUniqId parameter are present in your content with improperly escaped values.
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 · scopedUpdate ShopLentor plugin to version 3.3.9 or later which implements proper input sanitization and output escaping for the blockUniqId parameter.
ShopLentor version 3.3.9
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find the ShopLentor (WooCommerce Builder for Elementor & Gutenberg) plugin
- Click 'Update Now' if an update is available, or manually update to version 3.3.9
- Verify the update completed successfully
- Clear any caching layers (site cache, CDN cache)
- Test the Product Grid blocks to ensure functionality remains intact
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6287 — 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-2026-6287 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