dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-1000

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
The MailerLite - WooCommerce integration plugin for WordPress is vulnerable to unauthorized data modification and deletion in all versions up to, and including, 3.1.3. This is due to missing capability checks on the resetIntegration() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to reset the plugin's integration settings, delete all plugin options, and drop the plugin's database tables (woo_mailerlite_carts and woo_mailerlite_jobs), resulting in complete loss of plugin data including customer abandoned cart information and sync job history.

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 · high confidence

The MailerLite WooCommerce plugin has a broken access control vulnerability in the resetIntegration() function, which lacks capability checks. This allows any authenticated user with Subscriber-level permissions to reset integration settings, delete all plugin options, and drop the woo_mailerlite_carts and woo_mailerlite_jobs database tables, resulting in complete data loss.

MitigationUpdate to version 3.1.4 or later which implements proper capability checks on the resetIntegration() function. Verify the update in a staging environment before deploying to production.

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
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 MailerLite WooCommerce plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins, locate MailerLite for WooCommerce, and note the version number displayed. Alternatively, check the plugin's main PHP file (usually /wp-content/plugins/mailerlite-mailerlite-woocommerce/) for the version header in the plugin comment block.
    Affected if The installed version is lower than 3.1.4 (the fixed version) or cannot be determined.
  2. Verify if the resetIntegration function lacks capability checks
    Access the plugin files via FTP or file manager. Open the file containing resetIntegration() (typically in includes/ or src/ directory). Search for the function definition and examine whether it includes capability checks such as 'manage_options' or 'administrator' before executing the reset logic.
    Affected if The resetIntegration() function exists and does not contain any capability checks (e.g., no current_user_can() call with appropriate capability).
  3. Confirm the vulnerable REST API endpoint is registered without authorization
    Search the plugin code for REST route registration related to 'reset-integration' or 'resetIntegration'. Examine the permission_callback argument in the register_rest_route() call to see if it allows subscriber-level users or returns true without verification.
    Affected if A REST endpoint for resetIntegration is registered and the permission_callback permits any authenticated user (including Subscriber role).
  4. Check for the presence of the vulnerable database tables
    Access phpMyAdmin or run MySQL query: SHOW TABLES LIKE 'woo_mailerlite_%'; to list tables starting with this prefix. Identify if woo_mailerlite_carts and woo_mailerlite_jobs tables exist.
    Affected if The database tables exist and the plugin version is below 3.1.4, indicating the tables could be dropped by an attacker.

You are affected if the MailerLite WooCommerce plugin version is below 3.1.4 AND the resetIntegration() function or its REST endpoint lacks proper capability checks, allowing any authenticated Subscriber-level user to access it.

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 3.1.4 or later which implements proper capability checks on the resetIntegration() function. Verify the update in a staging environment before deploying to production.

Recommended fix Moderate confidence

Version 3.1.4 or later (latest stable release)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find the MailerLite - WooCommerce plugin
  4. Click 'Update Now' if an update is available, or manually download the latest version from WordPress.org and upload it
  5. After updating, verify the integration settings are still configured correctly
  6. Test that cart tracking and sync jobs are functioning normally
Caveat Minor: Review integration settings after upgrade as they may need reconfiguration

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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