Security readout for executives and security teams
Plain-English summary
This is a medium-severity CSRF issue in the MailerLite WooCommerce integration for WordPress, affecting versions through 2.0.8. A malicious site could potentially cause a logged-in WordPress user’s browser to perform an unintended plugin action. The public sources do not describe the exact action, fixed version, or observed exploitation.
Executive priority
Treat this as a routine but real WordPress plugin risk. Prioritize sites that connect WooCommerce customer or marketing workflows to MailerLite, especially externally managed stores. Address during the next maintenance window unless local evidence shows suspicious admin activity.
Technical view
CVE-2023-52223 is CWE-352 in the WordPress plugin woo-mailerlite. CVSS 3.1 is 5.4: network reachable, low complexity, no attacker privileges, user interaction required, no confidentiality impact, low integrity and availability impact. Public data identifies affected versions through 2.0.8 but does not include exploit details or remediation specifics.
Likely exposure
Exposure is likely limited to WordPress/WooCommerce sites running MailerLite – WooCommerce integration through version 2.0.8. The source bundle does not identify the vulnerable endpoint, affected role, or exact action, so scope should be confirmed against local installations and vendor guidance.
Exploitation context
No CISA KEV listing is provided, and the cited sources do not claim active exploitation. CSRF generally requires user interaction, such as a logged-in user visiting attacker-controlled content, but the public bundle does not provide exploit mechanics.
Researcher notes
The public record is sparse: it names CSRF, affected plugin, affected versions, CWE, and CVSS, but not the vulnerable action, nonce failure location, affected capability, fixed version, or exploit status. Avoid asserting exploitation or impact beyond low integrity and availability effects.
Mitigation direction
- Inventory WordPress sites for the woo-mailerlite plugin.
- Disable the plugin where it is not business-critical.
- Check MailerLite, WordPress.org, or Patchstack for fixed-version guidance.
- Update only to a vendor-confirmed non-vulnerable release.
- Limit WordPress admin access to trusted users.
- Monitor plugin-related settings or integration changes.
Validation and detection
- Confirm whether woo-mailerlite is installed on each WordPress site.
- Record installed plugin versions and flag versions through 2.0.8.
- Review vendor or Patchstack guidance for the fixed release.
- Check recent admin activity for unexpected MailerLite integration changes.
- Verify plugin updates in staging before production rollout.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-52223 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.