ShopengineWordPress extension · Wpmet
CVE-2022-45371
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 Wpmet ShopEngine plugin <= 4.1.1 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 the ShopEngine WordPress/WooCommerce plugin versions 4.1.1 and below allows attackers to induce authenticated users to perform unintended actions by tricking them into visiting malicious URLs or 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
ShopengineWordPress extension
<= 4.1.1CVSS 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.
-
Identify ShopEngine plugin installationNavigate to WordPress admin > Plugins and locate 'ShopEngine' in the installed plugins list, or check the plugin files in /wp-content/plugins/shopengine/ for the main plugin file containing version informationAffected if ShopEngine plugin is not installed or has been removed entirely (not affected)
-
Determine installed ShopEngine versionIn WordPress admin > Plugins, view the 'Version' column for ShopEngine, or open the main plugin PHP file (usually shopengine.php) and locate the 'Version' header in the plugin comment blockAffected if Installed version is 4.1.1 or lower (potentially affected)
-
Verify WooCommerce integration is activeConfirm WooCommerce is installed and active, as ShopEngine is a WooCommerce addon - check in WordPress admin > Plugins for WooCommerce statusAffected if WooCommerce is not active (the CSRF flaw only applies when ShopEngine can process WooCommerce-related state-changing operations)
-
Inspect plugin code for nonce implementationExamine ShopEngine PHP files for forms and AJAX handlers that perform state-changing operations (settings changes, cart actions, order processing); search for presence of wp_verify_nonce, check_admin_referer, or nonce_field function callsAffected if State-changing operations lack nonce verification or token validation (vulnerable to CVE-2022-45371)
-
Test for referer header validationReview PHP handlers in ShopEngine for server-side validation of HTTP_REFERER or Origin headers before processing requestsAffected if No referer/origin validation exists on sensitive operations (vulnerable to CSRF exploitation)
You are affected if ShopEngine plugin version 4.1.1 or lower is installed with WooCommerce active, and the plugin lacks proper nonce tokens or referer validation on state-changing operations.
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 (nonces) on all state-changing operations (forms, AJAX requests) and validate the token origin/referer header on the server side before processing requests.
Fix this in Shopengine
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45371 — 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-45371 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