CVE-2023-23868
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 WPFactory Cost of Goods for WooCommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Cost of Goods for WooCommerce: from n/a through 2.8.6.
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 WPFactory Cost of Goods for WooCommerce (versions through 2.8.6) allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized users to access or modify cost of goods data they should not have permission to view or change.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
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.
-
Confirm plugin is installedNavigate to WordPress admin > Plugins and locate 'Cost of Goods for WooCommerce' by WPFactory, or check the plugins directory for the cost-of-goods-for-woocommerce folderAffected if The plugin is installed and active
-
Identify installed versionIn WordPress admin > Plugins, find the plugin and read the version number displayed beneath the plugin name, or check the main plugin file for the 'Version' header commentAffected if Version is 2.8.6 or lower (the affected range is through version 2.8.6)
-
Review user role access settingsGo to WordPress admin > Users > User Role Editor or use a role management plugin to examine what capabilities are assigned to roles below Administrator, specifically looking for 'manage_cost_of_goods' or similar cost/goods-related capabilitiesAffected if Non-administrator roles (Shop Manager, Customer, or custom roles) have capabilities to view or edit cost of goods data when they should not
-
Test for unauthorized accessUsing a low-privileged user account (such as a Customer or Subscriber), attempt to access the Cost of Goods settings page or API endpoints (typically under WooCommerce > Settings > Products > Cost of Goods, or via wp-json/wc/v3/ endpoints)Affected if The low-privileged user can view, modify, or access cost data they should not have permission to see
You are affected if the Cost of Goods for WooCommerce plugin is installed at version 2.8.6 or lower AND non-privileged users can access or modify cost of goods data due to missing authorization checks.
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 to the latest version of Cost of Goods for WooCommerce and review user role permissions to ensure proper access controls are enforced.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23868 — 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-23868 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