Wp ShopWordPress extension
CVE-2022-36793
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 · uneditedUnauthenticated Plugin Settings Change & Data Deletion vulnerabilities in WP Shop plugin <= 3.9.6 at WordPress.
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 WP Shop plugin for WordPress versions 3.9.6 and below contains two critical vulnerabilities allowing unauthenticated attackers to modify plugin settings and delete data without any authentication credentials.
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
Wp ShopWordPress extension
<= 3.9.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Verify WP Shop plugin is installedLog in to WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'WP Shop' or 'Wp Shop Wp Shop' in the list of active pluginsAffected if The WP Shop plugin appears in the installed plugins list regardless of activation status
-
Identify installed WP Shop versionIn WordPress admin, go to Plugins > Installed Plugins, find WP Shop, and note the version number displayed next to the plugin name. Alternatively, check the plugin header in wp-content/plugins/wpshop/main.php for the 'Version' fieldAffected if The displayed version number is 3.9.6 or lower
-
Confirm unauthenticated access exposureTest access to plugin AJAX endpoints or admin-ajax.php with WPShop actions without providing any authentication cookies or credentials. Use a tool like curl: curl -X POST https://yoursite.com/wp-admin/admin-ajax.php -d 'action=wpshop_some_action'Affected if The server returns a successful response instead of an authentication error or 403 Forbidden
-
Check for recent unauthorized changesReview WordPress activity logs, server access logs, or plugin settings for any unauthorized modifications to WP Shop configuration, especially settings related to product data, orders, or deletions that occurred without admin loginAffected if There are settings modifications or data deletions in logs that were not performed by an authenticated administrator
A WordPress site is affected if the WP Shop plugin version 3.9.6 or lower is installed and the plugin exposes unauthenticated access to modify settings or delete data.
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 the WP Shop plugin to a version newer than 3.9.6 immediately. If no patched version is available, disable the plugin or restrict access to administrative functions at the web server level.
Fix this in Wp Shop
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36793 — 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-36793 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