CVE-2023-32299
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 Anzar Ahmed Ni WooCommerce Sales Report ni-woocommerce-sales-report allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Ni WooCommerce Sales Report: from n/a through <= 3.7.3.
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 Ni WooCommerce Sales Report plugin version 3.7.3 and earlier contains a missing authorization vulnerability (CWE-862) where the plugin fails to properly verify user capabilities before allowing access to sales report data, potentially allowing authenticated users without proper permissions to view sensitive business information.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 NI WooCommerce Sales Report plugin is installedLog into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Locate 'NI WooCommerce Sales Report' in the list and note the version number displayed. Alternatively, check the plugin's main PHP file (typically in /wp-content/plugins/ni-woocommerce-sales-report/) for the 'Version' header in the plugin comment block.Affected if The plugin is installed and the reported version is 3.7.3 or lower.
-
Confirm WooCommerce is activeIn the WordPress admin under Plugins > Installed Plugins, verify that WooCommerce is installed and activated. This plugin is a WooCommerce extension and requires WooCommerce to function.Affected if WooCommerce is not installed or not activated.
-
Compare installed version to affected rangeTake the version number identified in step 1 and compare it against the affected versions: any version 3.7.3 or earlier is vulnerable. The version number is typically formatted as '3.7.3' or similar in the plugin metadata.Affected if The installed version is 3.7.3 or any version number that resolves to 3.7.3 or earlier (e.g., 3.7.2, 3.7.1, 3.7.0, 3.6.x).
-
Test sales report endpoint access with low-privilege userCreate or use an existing WordPress user role with minimal permissions (e.g., Subscriber). Attempt to access the sales report page directly via the plugin's URL endpoint (commonly /wp-admin/admin.php?page=ni-woocommerce-sales-report or similar). Observe whether the page loads and displays sensitive business data without prompting for elevated privileges.Affected if The sales report page loads and displays business information to a user account that lacks the 'manage_options' or equivalent administrative capability.
A user is affected if the NI WooCommerce Sales Report plugin version is 3.7.3 or earlier AND WooCommerce is active AND sales report data is accessible to users without proper administrative capabilities.
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 dataAdd proper capability checks (e.g., current_user_can()) and nonce verification on all sales report endpoints; update to the latest plugin version once the vendor releases a patch.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32299 — 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-32299 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