Ecommerce Product CatalogWordPress extension · Implecode
CVE-2023-5979
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 eCommerce Product Catalog Plugin for WordPress plugin before 3.3.26 does not have CSRF checks in some of its admin pages, which could allow attackers to make logged-in users perform unwanted actions via CSRF attacks, such as delete all products
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 eCommerce Product Catalog Plugin for WordPress versions prior to 3.3.26 lack CSRF token validation in certain admin action endpoints. This allows an attacker to craft malicious links that, when clicked by a logged-in administrator, can trigger unintended actions such as bulk deletion of products, because the server trusts requests from an authenticated user without verifying the request origin.
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
Ecommerce Product CatalogWordPress extension
< 3.3.26CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 the eCommerce Product Catalog plugin is installedLog into WordPress admin and navigate to Plugins > Installed Plugins, or use FTP/shell to check the wp-content/plugins directory for a folder named 'ecommerce-product-catalog' or similarAffected if The plugin folder does not exist or the plugin is not listed among installed plugins in WordPress
-
Determine the installed plugin versionIn WordPress Admin under Plugins > Installed Plugins, locate 'eCommerce Product Catalog' and read the version number displayed beneath the plugin name, or open the main plugin PHP file (such as ecommerce-product-catalog.php) and inspect the 'Version' header in the file comment blockAffected if The version number cannot be retrieved from the plugin header or WordPress admin interface
-
Compare version to affected rangeCompare the installed version number to 3.3.26 - any version lower than 3.3.26 falls within the affected range (for example: 3.3.25, 3.3.20, 3.2.0, 2.9.8, etc.)Affected if The installed version is less than 3.3.26 (for example 3.3.25, 3.3.0, 3.0.0, etc.)
Your environment is affected if the eCommerce Product Catalog plugin is installed and its version is below 3.3.26, because the missing CSRF token validation affects only versions prior to 3.3.26.
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 · scoped3.3.26
Update the eCommerce Product Catalog Plugin to version 3.3.26 or later which implements proper CSRF token verification on sensitive admin actions.
3.3.26
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find the 'Ecommerce Product Catalog' plugin
- Check if an update is available (or manually update to version 3.3.26)
- If automatic update is available, click 'Update Now'
- If manual update is needed, download version 3.3.26 from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
- After updating, verify the plugin version shows 3.3.26 or higher
- Test that admin functionality still works correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ecommerce Product Catalog
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5979 — 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-2023-5979 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