dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-29174

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Missing Authorization vulnerability in NervyThemes SKU Label Changer For WooCommerce.This issue affects SKU Label Changer For WooCommerce: from n/a through 3.0.

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 confidence

Missing authorization vulnerability in SKU Label Changer For WooCommerce plugin allows low-privileged users (likely shop managers or users with some backend access) to modify SKU labels without proper capability checks. The plugin fails to verify user permissions before allowing changes to product SKU settings, potentially enabling unauthorized modification of product identifiers.

MitigationImplement proper authorization checks (using WordPress capability checks like 'manage_woocommerce' or 'edit_products') and nonce verification on all admin AJAX endpoints and admin pages that modify SKU data. Restrict SKU label changes to users with appropriate WooCommerce permissions.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if SKU Label Changer For WooCommerce is installed
    In WordPress admin, go to Plugins > Installed Plugins and search for 'SKU Label Changer For WooCommerce' or check the /wp-content/plugins/ directory for a folder containing 'sku-label' in the name
    Affected if The plugin is installed and active
  2. Check the installed plugin version
    In WordPress admin, click on the plugin from the installed plugins list to view its version details, or read the main plugin file header in /wp-content/plugins/[plugin-folder]/sku-label-changer.php
    Affected if The version matches or falls within any known affected version range (compare your version to the affected ranges if publicly disclosed)
  3. Verify user roles with SKU modification access
    Go to WordPress Users > All Users and review which users have roles that might include shop_manager or custom roles with WooCommerce access; cross-reference with who should legitimately have SKU edit capabilities
    Affected if Users with low-privilege roles (such as shop_manager or lower) have access to the SKU Label Changer functionality
  4. Test AJAX endpoint accessibility for authorization
    Use a tool like curl or a browser dev console to send a POST request to wp-admin/admin-ajax.php with action=sku_label_changer_update (or similar SKU-related action) while logged in as a low-privilege user, observing if the request succeeds without a capability error
    Affected if The AJAX endpoint accepts and processes requests from users lacking manage_woocommerce or edit_products capabilities
  5. Audit for unauthorized SKU modifications
    Check WordPress activity logs or WooCommerce product history for recent changes to product SKUs; alternatively, query the wp_posts table in the database for recent post_modified timestamps on products where user_id is unexpected
    Affected if SKU changes exist that were performed by users without proper WooCommerce permissions

A user is affected if the SKU Label Changer For WooCommerce plugin is installed and low-privileged users can modify SKU labels without proper capability verification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks (using WordPress capability checks like 'manage_woocommerce' or 'edit_products') and nonce verification on all admin AJAX endpoints and admin pages that modify SKU data. Restrict SKU label changes to users with appropriate WooCommerce permissions.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-29174 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-29174 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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