dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-32441

HIGH · 7.7 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable 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 WebToffee Comments Import & Export comments-import-export-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Comments Import & Export: from n/a through <= 2.4.9.

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 WebToffee Comments Import & Export plugin for WooCommerce. The vulnerability allows attackers to exploit incorrectly configured access control security levels, likely enabling unauthorized users to access comment import/export functionality they should not have permission to use.

MitigationApply the latest security patch (version 2.5.0 or later) from WebToffee which should include proper capability/authorization checks on all admin functions. Until patched, restrict admin access to trusted personnel only.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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. Identify the installed plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > Look for 'WebToffee Comments Import & Export' and check the version number displayed under the plugin name
    Affected if The version number displayed is lower than 2.5.0 or the version cannot be determined (plugin may be outdated)
  2. Verify the plugin is active
    In the same plugins list, confirm the WebToffee Comments Import & Export plugin shows as 'Active'
    Affected if The plugin is active and the version is below 2.5.0
  3. Check for comment import/export menu access
    Look in the WordPress admin sidebar for a menu item related to comment import/export (typically under WooCommerce or a WebToffee menu section). Note which user roles can see this menu
    Affected if Users with roles other than Administrator (such as Editor, Shop Manager, or custom roles) can see or access the comment import/export functionality
  4. Test unauthorized role access
    Log in with a non-administrator user role (e.g., Editor or Shop Manager) and attempt to access the comment import/export page directly via URL or navigation menu
    Affected if A non-administrator user can successfully access and use the comment import/export features without being blocked or redirected
  5. Review user role capabilities
    Navigate to WordPress admin > Users > Roles (or use a role management plugin) to examine what capabilities are assigned to non-administrator roles related to comment management
    Affected if Non-administrator roles have capabilities that allow comment import/export operations (such as 'manage_woocommerce' or specific comment export permissions)

You are affected if the WebToffee Comments Import & Export plugin is active, the installed version is below 2.5.0, and non-administrator users can access or use the comment import/export functionality 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the latest security patch (version 2.5.0 or later) from WebToffee which should include proper capability/authorization checks on all admin functions. Until patched, restrict admin access to trusted personnel only.

Recommended fix Moderate confidence

Upgrade to Comments Import & Export for WooCommerce version 2.4.10 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the "Comments Import & Export for WooCommerce" (WebToffee) plugin
  4. 4. If an update is available, click "Update Now" to upgrade to the latest version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository or WebToffee's official website
  6. 6. Deactivate and delete the current plugin version
  7. 7. Upload and install the new version
  8. 8. Reactivate the plugin

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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