Premmerce Product Filter For WoocommerceWordPress extension · Premmerce
CVE-2024-31359
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 · uneditedMissing Authorization vulnerability in Premmerce Premmerce Product Filter for WooCommerce premmerce-woocommerce-product-filter.This issue affects Premmerce Product Filter for WooCommerce: from n/a through <= 3.7.2.
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 confidenceMissing Authorization vulnerability in Premmerce Product Filter for WooCommerce plugin allows authenticated users (with subscriber-level access or higher) to perform actions they should not have permission to execute. The plugin fails to properly validate user capabilities before performing sensitive operations, enabling privilege escalation or unauthorized data access.
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
Premmerce Product Filter For WoocommerceWordPress extension
< 3.7.3CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.
-
Verify the Premmerce Product Filter plugin is installedLog in to WordPress admin, go to Plugins > Installed Plugins, and look for 'Premmerce Product Filter for WooCommerce' in the listAffected if The plugin is present in the WordPress installation
-
Check the installed plugin versionIn the Plugins list, locate Premmerce Product Filter for WooCommerce and note the version number displayed beneath the plugin nameAffected if The version number is lower than 3.7.3 (e.g., 3.7.2, 3.6.x, etc.)
-
Confirm WordPress user roles existGo to Users > All Users in WordPress admin and review the role assigned to each user account (roles include Administrator, Editor, Author, Contributor, Subscriber)Affected if Any user account exists with Subscriber role or higher (this is the baseline condition required for the vulnerability to be exploitable)
-
Review admin activity logs for suspicious actionsCheck WordPress audit logs, activity logs, or security plugins for actions performed by users with Subscriber, Contributor, Author, or Editor roles that would typically require Administrator capabilitiesAffected if Actions appear in logs that were performed by non-Administrator users which should have required higher privileges
The environment is affected if the Premmerce Product Filter for WooCommerce plugin version is below 3.7.3 and any subscriber-level or higher user accounts exist in WordPress, as these users could potentially perform unauthorized privileged actions through the plugin.
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.7.3
Update to the patched version of Premmerce Product Filter for WooCommerce when available. If no patch exists, implement proper WordPress capability checks (current_user_can()) before sensitive operations and restrict admin actions to administrator-level users only.
3.7.3
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate 'Premmerce Product Filter for WooCommerce' in the plugin list
- 4. If an update is available, click 'Update Now' to upgrade to version 3.7.3
- 5. Alternatively, navigate to Dashboard > Updates and select the plugin to update
- 6. After updating, verify the plugin version shows 3.7.3
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Premmerce Product Filter For Woocommerce
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31359 — 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-2024-31359 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