Woolentor Woocommerce Elementor Addons \+ BuilderWordPress extension · Hasthemes
CVE-2022-47172
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in HasThemes ShopLentor plugin <= 2.6.2 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 confidenceCross-Site Request Forgery (CSRF) vulnerability in HasThemes ShopLentor plugin versions 2.6.2 and below allows attackers to trick authenticated administrators into unknowingly executing unwanted actions within the plugin by leveraging the lack of proper CSRF token validation on state-changing requests.
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
<= 2.6.2CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 installed plugin versionNavigate to WordPress admin > Plugins > Installed Plugins, locate Woolentor (ShopLentor) and note the version number displayedAffected if Version is 2.6.2 or lower (e.g., 2.6.2, 2.6.1, 2.6.0, etc.)
-
Identify plugin admin pagesAccess the Woolentor/ShopLentor settings pages in WordPress admin (typically under Woolentor or Elementor menu)Affected if You can access admin pages where you can modify settings, create layouts, or change plugin configurations
-
Inspect form HTML for CSRF tokensRight-click any form in the Woolentor admin settings > Inspect Element, look for hidden input fields named like 'nonce', 'csrf', 'token', or '_wpnonce' inside the form tagsAffected if No hidden token/nonce field is present in forms that change settings, save layouts, or modify plugin data
-
Check AJAX requests for token validationOpen browser DevTools > Network tab, trigger a state-changing action (save settings, add element, delete item), inspect the AJAX request headers and payload for a nonce or token parameterAffected if AJAX requests to wp-admin/admin-ajax.php from this plugin do not include a nonce/token parameter in the request body or headers
If the installed Woolentor/ShopLentor version is 2.6.2 or below AND forms/AJAX actions lack CSRF token validation, the environment is affected by this 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 dataImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations and validate Origin/Referer headers to ensure requests originate from legitimate sources; ensure all form submissions and AJAX actions include and validate unique tokens.
Fix this in Woolentor Woocommerce Elementor Addons \+ Builder
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47172 — 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-2022-47172 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