dbcve.org
MailerliteWordPress extension

CVE-2023-52223

HIGH · 8.8 CVSS v3.1 Published 2024-02-28
Fix available
A fix is available. Upgrade to 2.0.9 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in MailerLite MailerLite – WooCommerce integration.This issue affects MailerLite – WooCommerce integration: from n/a through 2.0.8.

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

Cross-Site Request Forgery (CSRF) vulnerability in the MailerLite WooCommerce integration plugin allows attackers to trick authenticated administrators into performing unintended actions such as modifying plugin settings or synchronizing subscriber data without their consent.

MitigationUpgrade to version 2.0.9 or later which includes anti-CSRF token validation for state-changing operations. Until patched, admin actions should be closely monitored.

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
MailerliteWordPress extension
Affected:< 2.0.9

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 MailerLite WooCommerce plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and search for 'Mailerlite' or 'MailerLite WooCommerce Integration'. Alternatively, check the /wp-content/plugins/ directory for a folder named 'mailerlite' or similar.
    Affected if The MailerLite WooCommerce integration plugin appears in the installed plugins list
  2. Check installed plugin version
    In WordPress admin, click on the MailerLite plugin from the Plugins list and view the version number displayed. Alternatively, check the main plugin file (e.g., mailerlite.php) for the version comment header.
    Affected if The version displayed is lower than 2.0.9 (e.g., 2.0.8, 2.0.7, etc.)
  3. Confirm WordPress and WooCommerce are active
    Check that the site runs on WordPress and has WooCommerce installed and activated, as this is a WooCommerce integration plugin. Verify via Plugins > Installed Plugins or WooCommerce > Status.
    Affected if WooCommerce is installed and active on the WordPress site
  4. Verify absence of anti-CSRF token implementation
    Inspect the plugin's admin action handlers (typically in the main PHP file) for state-changing operations (settings saves, subscriber sync). Look for nonce verification or token validation calls before processing POST/GET requests.
    Affected if No nonce verification or anti-CSRF token validation is found before processing admin actions

The environment is affected if the MailerLite WooCommerce integration plugin is installed with a version below 2.0.9 on an active WordPress/WooCommerce site.

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 2.0.9 or later
Fixed in 2.0.9
Interim mitigation

Upgrade to version 2.0.9 or later which includes anti-CSRF token validation for state-changing operations. Until patched, admin actions should be closely monitored.

Recommended fix High confidence

Version 2.0.9 or later of MailerLite – WooCommerce integration plugin

  1. 1. Update MailerLite – WooCommerce integration plugin to version 2.0.9 or later
  2. 2. Verify the update was successful by checking the installed plugin version
  3. 3. Test critical WooCommerce workflows (e.g., subscription signups, order syncing) to ensure functionality is intact
Caveat Standard plugin update - review release notes for any configuration changes if moving across major version jumps

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

Fix this in Mailerlite 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 the upgrade done

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-2023-52223 — 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-2023-52223 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