dbcve.org
Advanced Linked Variations For WoocommerceWordPress extension · Multidots

CVE-2025-46244

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-22
Fix available
A fix is available. Upgrade to 1.0.4 or later.
See remediation →
100/100
Remediation priority · Urgent
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 Dotstore Advanced Linked Variations for Woocommerce linked-variation allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Advanced Linked Variations for Woocommerce: from n/a through <= 1.0.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 confidence

This is a Missing Authorization (Broken Access Control) vulnerability in the Dotstore Advanced Linked Variations for WooCommerce plugin. The plugin fails to properly enforce authorization checks on certain functionality, allowing attackers to exploit incorrectly configured access control security levels. This could enable unauthorized users to access or manipulate linked product variations that should require proper authentication and authorization.

MitigationImplement proper capability checks and authorization validation on all sensitive plugin functions. Update to the latest patched version when available. Until a patch is released, restrict access to the affected functionality via WAF rules or consider disabling the plugin if the risk is unacceptable.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Advanced Linked Variations For WoocommerceWordPress extension
Affected:< 1.0.4

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 installation
    Check if the Advanced Linked Variations for WooCommerce plugin is installed. In WordPress, navigate to Plugins > Installed Plugins and look for 'Advanced Linked Variations For WooCommerce' by Multidots, or check the filesystem at wp-content/plugins/ for a folder containing 'advanced-linked-variations' or similar.
    Affected if The plugin is installed and active in WordPress
  2. Determine installed version
    In WordPress admin, go to Plugins > Installed Plugins and click on the plugin to view details, or read the main plugin file (usually contains version in header). Alternatively, check the plugin folder for a readme.txt or index.php file that declares the version.
    Affected if The installed version is lower than 1.0.4 (e.g., 1.0.3, 1.0.2, etc.)
  3. Identify vulnerable AJAX endpoints
    Inspect the plugin PHP files for AJAX action handlers (search for 'add_action("wp_ajax_' or 'add_action("wp_ajax_nopriv_' calls) related to linked variation management functions. Common vulnerable patterns include endpoints for saving, updating, or deleting linked variations without capability checks.
    Affected if The plugin contains AJAX endpoints for linked variation management that do not include current_user_can() or similar authorization checks before processing requests
  4. Test for missing authorization
    If you have access to a low-privilege user account (e.g., subscriber or customer), attempt to access the suspected AJAX endpoints directly via POST requests to the wp-admin/admin-ajax.php endpoint, passing parameters that would modify linked variations. Check if the requests succeed without returning a permission denied response.
    Affected if Requests to linked variation management functions succeed without proper capability verification, allowing unauthorized modification of product variation data

You are affected if the Advanced Linked Variations For WooCommerce plugin is installed with a version lower than 1.0.4 and the plugin's variation management endpoints are accessible without proper authorization checks.

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
Upgrade available Upgrade to 1.0.4 or later
Fixed in 1.0.4
Interim mitigation

Implement proper capability checks and authorization validation on all sensitive plugin functions. Update to the latest patched version when available. Until a patch is released, restrict access to the affected functionality via WAF rules or consider disabling the plugin if the risk is unacceptable.

Recommended fix High confidence

Advanced Linked Variations For Woocommerce version 1.0.4

  1. 1. Back up your WordPress site and database before performing any updates.
  2. 2. Navigate to WordPress Admin Dashboard > Plugins > Installed Plugins
  3. 3. Find 'Advanced Linked Variations For Woocommerce' (by Dotstore) in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.0.4
  5. 5. Alternatively, go to Dashboard > Updates to check for and apply the update
  6. 6. After updating, verify the plugin status shows version 1.0.4
  7. 7. Test that the linked variations functionality works correctly in your WooCommerce store
  8. 8. Confirm the authorization controls are properly enforced by testing access to the linked-variation functionality

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

Fix this in Advanced Linked Variations For Woocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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