Wpc Frequently Bought Together For WoocommerceWordPress extension · Wpclever
CVE-2024-43312
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 WPClever WPC Frequently Bought Together for WooCommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WPC Frequently Bought Together for WooCommerce: from n/a through 7.1.9.
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 the WPClever WPC Frequently Bought Together WooCommerce plugin allows attackers to exploit incorrectly configured access control security levels. The plugin fails to properly validate user permissions before allowing access to certain functionality, potentially enabling unauthorized actions.
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
Wpc Frequently Bought Together For WoocommerceWordPress extension
< 7.2.0CVSS 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 plugin is installedNavigate to WordPress admin > Plugins and look for 'Wpc Frequently Bought Together' or 'WPC Frequently Bought Together for WooCommerce' in the installed plugins listAffected if The plugin appears in the installed plugins list
-
Identify installed versionIn WordPress admin > Plugins, find the WPC Frequently Bought Together plugin and locate the version number displayed below the plugin nameAffected if Version number is visible and is below 7.2.0
-
Compare against affected rangeCompare your installed version to the affected range: any version below 7.2.0 is within the vulnerable rangeAffected if Installed version is less than 7.2.0 (for example, 7.1.9, 7.1.0, etc.)
-
Assess user account exposureReview WordPress users page to determine if the site has multiple user accounts with different roles beyond just a single administratorAffected if Multiple user accounts exist with roles such as editor, author, or subscriber, indicating the authorization flaw could be exploited
-
Check for unauthorized access indicatorsReview WooCommerce settings and any custom links or endpoints created by the plugin to verify if unauthenticated or lower-privilege users can access normally restricted plugin featuresAffected if Lower-privileged users can access plugin administrative functions or data they should not have permission to view
If the installed version is below 7.2.0 and the site has multiple user accounts, the environment is likely affected by this missing authorization 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.
dbcve · scoped7.2.0
Update the WPC Frequently Bought Together plugin to the latest version (7.1.10 or later) which contains the patched authorization controls. If updates are unavailable, consider disabling the plugin or restricting access at the web server level.
7.2.0
- Backup your WordPress site and database before making any changes
- Update WPC Frequently Bought Together for WooCommerce to version 7.2.0 or later via the WordPress plugin repository, or upload the latest version manually
- Verify the update was successful by checking the installed version number
- Test the plugin functionality to ensure the update did not break expected features
- Review user roles and permissions to confirm proper access controls are now enforced
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wpc Frequently Bought Together For Woocommerce
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-2024-43312 — 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-43312 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