dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-46635

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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 YITHEMES YITH WooCommerce Product Add-Ons yith-woocommerce-product-add-ons allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects YITH WooCommerce Product Add-Ons: from n/a through <= 4.2.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 YITH WooCommerce Product Add-Ons plugin allows attackers to exploit incorrectly configured access control security levels, potentially accessing functionality that should be restricted to authorized users.

MitigationUpdate to version 4.2.1 or later which contains proper authorization controls; if no update available, audit the plugin's admin ajax handlers and privileged functions for missing capability checks and add appropriate WordPress capability verifications.

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checks

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

  1. Verify the YITH WooCommerce Product Add-Ons plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'YITH WooCommerce Product Add-Ons' in the list of active plugins.
    Affected if The plugin is present in the WordPress installation and is activated
  2. Identify the installed plugin version
    In the Plugins page, click on the plugin name to view its details, or check the plugin header in the main plugin file (typically in wp-content/plugins/yith-woocommerce-product-add-ons/) for the Version field.
    Affected if The version number is lower than 4.2.1 (e.g., 4.0.0, 3.x.x, etc.)
  3. Inspect admin ajax handlers for missing capability checks
    Examine the plugin files in the includes/admin/ajax/ directory (or similar paths containing 'ajax' handlers). Look for WordPress capability verification functions such as 'current_user_can', 'check_ajax_referer', or 'wp_verify_nonce' at the beginning of ajax action handlers.
    Affected if Ajax handlers that modify product add-on settings or perform privileged actions lack proper capability checks or nonce verification
  4. Audit privileged function access controls
    Review PHP files in the plugin includes/admin/ directory (or any file containing 'admin' in the path) for functions that should be restricted to administrators. Search for functions accessing _POST, _GET, or $_REQUEST parameters without preceding capability checks.
    Affected if Functions that create, update, or delete product add-ons can be accessed by any authenticated user including subscribers or customers
  5. Test external access to vulnerable endpoints
    If you have a staging environment, use a low-privilege user account (e.g., subscriber role) to attempt accessing admin-ajax.php with the plugin's action names (such as 'yith_wcpa_save_addon' or similar) via curl or browser developer tools.
    Affected if Requests from unprivileged accounts successfully execute actions that should require administrator capabilities

Your environment is affected if the YITH WooCommerce Product Add-Ons plugin is installed with a version lower than 4.2.1 and the plugin's admin ajax handlers or privileged functions lack WordPress capability checks, allowing unauthorized users to modify add-on settings.

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

Update to version 4.2.1 or later which contains proper authorization controls; if no update available, audit the plugin's admin ajax handlers and privileged functions for missing capability checks and add appropriate WordPress capability verifications.

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-46635 — 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-46635 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