dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-68025

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 Floating Cart For WooCommerce addonify-floating-cart allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Addonify Floating Cart For WooCommerce: from n/a through <= 1.2.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

This is a missing authorization vulnerability in the Addonify Floating Cart For WooCommerce plugin. The plugin has access control mechanisms but they are incorrectly configured, allowing authenticated users to access functionality they should not be permitted to use. This could enable lower-privileged users to perform administrative or privileged actions within the plugin.

MitigationApply the vendor patch when available. Until then, restrict administrative access to the site and consider disabling the plugin if the vulnerable functionality is not essential. Review user role assignments and ensure only trusted users have account access.

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. Verify plugin is installed
    Check if Addonify Floating Cart For WooCommerce plugin is installed and active in WordPress via Plugins admin page or by checking /wp-content/plugins/ directory
    Affected if Plugin is present and active in the WordPress installation
  2. Identify installed version
    Check the plugin version in WordPress plugin admin page, or read the main plugin file header in /wp-content/plugins/addonify-floating-cart-for-woocommerce/ to find the Version field
    Affected if Cannot determine version - plugin is installed but version information is inaccessible
  3. Confirm WooCommerce is active
    Verify WooCommerce is installed and active, as this is a WooCommerce-specific plugin that requires WooCommerce to function
    Affected if WooCommerce is not installed or not active
  4. Check user role access to plugin features
    Review user roles in WordPress admin and test whether non-administrator users (editors, authors, subscribers, customers) can access plugin settings or perform actions that should require administrator privileges
    Affected if Lower-privileged authenticated users can access plugin administrative functions or settings they should not be able to modify

User is affected if the Addonify Floating Cart For WooCommerce plugin is installed and allows authenticated non-administrator users to access privileged plugin functionality due to missing authorization controls.

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

Apply the vendor patch when available. Until then, restrict administrative access to the site and consider disabling the plugin if the vulnerable functionality is not essential. Review user role assignments and ensure only trusted users have account access.

Recommended fix Moderate confidence

Latest version of Addonify Floating Cart For WooCommerce (version > 1.2.17)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Addonify Floating Cart For WooCommerce' in the plugin list
  4. Check if the current version is 1.2.17 or earlier
  5. If vulnerable, click 'Update now' when an update is available, or manually download the latest version from wordpress.org/plugins/addonify-floating-cart-for-woocommerce/
  6. After updating, verify the new version number reflects the update
  7. Test cart functionality on the frontend to ensure the plugin still works correctly after the update

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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