dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-68023

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-20
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 Addonify Addonify – Compare Products For WooCommerce addonify-compare-products allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Addonify – Compare Products For WooCommerce: from n/a through <= 1.1.17.

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 the Addonify Compare Products for 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 users to access sensitive comparison features or data.

MitigationUpdate to version 1.1.18 or later which contains proper authorization controls. If immediate update is not possible, audit the plugin's access control implementation and add capability checks and nonce validation to all admin/frontend functions.

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. Confirm Addonify Compare Products plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Addonify Compare Products for WooCommerce' in the list of installed plugins
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed plugin version
    Click on the plugin name or view details to find the version number displayed (typically below the plugin name)
    Affected if Version is lower than 1.1.18 or the version cannot be determined
  3. Verify WooCommerce is active
    Check that WooCommerce plugin status shows as 'Active' in the WordPress Plugins page, since this is a WooCommerce extension
    Affected if WooCommerce is active and the addon plugin is installed
  4. Check for exposed AJAX or REST endpoints
    Inspect page source or use browser developer tools to look for AJAX calls or REST API endpoints belonging to addonify-compare-products (paths typically contain 'addonify-compare' or 'acp')
    Affected if Publicly accessible AJAX/REST endpoints exist without capability checks
  5. Review user role access to plugin features
    Navigate to plugin settings page (Addons > Compare Products) and check if there are access control options or if any non-administrator user roles can access comparison data
    Affected if Settings allow unrestricted access to comparison features without role verification

If the plugin is installed with a version before 1.1.18 and WooCommerce is active, the environment is likely affected by this authorization bypass vulnerability.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 1.1.18 or later which contains proper authorization controls. If immediate update is not possible, audit the plugin's access control implementation and add capability checks and nonce validation to all admin/frontend functions.

Recommended fix Moderate confidence

Version 1.1.18 or later (latest available version)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Addonify – Compare Products For WooCommerce'
  4. 4. Check the current version number displayed under the plugin name
  5. 5. If the version is 1.1.17 or earlier, click 'Update Now' to install the latest available version
  6. 6. Alternatively, download the latest version from the WordPress plugin repository or from Addonify's official source
  7. 7. After updating, verify the plugin is functioning correctly on your site

Generated from the published advisory — verify against the referenced sources before acting.

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

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-68023 — 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-2025-68023 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