Security readout for executives and security teams
Plain-English summary
This is a CSRF issue in the Mercado Pago payments for WooCommerce WordPress plugin through version 6.3.1. An attacker may be able to trick a site user into causing an unintended change. The public bundle indicates low integrity impact, not data theft or outage.
Executive priority
Treat as a routine but timely e-commerce hygiene issue. It is not documented as actively exploited, but payment plugins affect revenue operations, so confirm versions and remediation status soon.
Technical view
CVE-2022-45068 is CWE-352 affecting package woocommerce-mercadopago, Mercado Pago payments for WooCommerce <= 6.3.1. CVSS 3.1 is 4.3: network attack, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact only.
Likely exposure
Exposure is limited to WordPress WooCommerce sites running the Mercado Pago payments for WooCommerce plugin at version 6.3.1 or earlier. Sites not using this plugin are not indicated as affected.
Exploitation context
The source bundle does not report active exploitation, and the CVE is not marked KEV. Successful abuse requires user interaction. The exact vulnerable action is not described in the provided evidence.
Researcher notes
The public bundle gives severity, affected plugin, CWE, and CVSS, but not the vulnerable endpoint, fixed version, or specific state-changing action. Avoid assuming exploitability details beyond CSRF with required user interaction.
Mitigation direction
- Identify all WordPress sites using the Mercado Pago WooCommerce plugin.
- Check vendor or Patchstack guidance for the fixed version or recommended mitigation.
- Upgrade affected installations when a vendor-supported fixed release is confirmed.
- Disable the plugin where business impact allows until remediation is verified.
- Limit administrative access and reduce exposure to untrusted browsing sessions.
Validation and detection
- Confirm whether woocommerce-mercadopago is installed on each WooCommerce site.
- Record the installed plugin version and compare it with <= 6.3.1.
- Check vendor release notes or Patchstack for remediation status.
- Review payment plugin settings for unexpected changes.
- Document any site where the fix path cannot be confirmed.
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-2022-45068 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
- 4.3 (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:N
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:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/vulnerability/woocommerce-mercadopago/wordpress-mercado-pago-payments-for-woocommerce-plugin-6-3-1-cross-site-request-forgery-csrf-vulnerability?_s_id=cveCVE reference · vdb-entry
- https://patchstack.com/database/vulnerability/woocommerce-mercadopago/wordpress-mercado-pago-payments-for-woocommerce-plugin-6-3-1-cross-site-request-forgery-csrf-vulnerability-2?_s_id=cveCVE reference · vdb-entry
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.