dbcve.org
Mercado Pago Payments For WoocommerceWordPress extension · Mercadopago

CVE-2022-45068

HIGH · 8.8 CVSS v3.1 Published 2023-03-01
Fix available
A fix is available. Upgrade to 6.4.0 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 Mercado Pago Mercado Pago payments for WooCommerce plugin <= 6.3.1.

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

A Cross-Site Request Forgery (CSRF) vulnerability exists in the Mercado Pago payments for WooCommerce plugin for WordPress versions 6.3.1 and below. This allows attackers to trick authenticated administrators or users into performing unintended state-changing actions, such as modifying payment settings or processing transactions, by leveraging the site's trust in the user's authenticated session.

MitigationImplement anti-CSRF tokens (nonce validation) on all state-changing operations and forms within the plugin, and update to a patched version if available from the vendor.

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
Mercado Pago Payments For WoocommerceWordPress extension
Affected:< 6.4.0

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 the Mercado Pago plugin is installed
    Navigate to WordPress Admin > Plugins and locate 'Mercado Pago Payments for WooCommerce' in the installed plugins list
    Affected if the plugin is not found in the plugins list
  2. Confirm the plugin is active
    In WordPress Admin > Plugins, check if 'Mercado Pago Payments for WooCommerce' shows as 'Active'
    Affected if the plugin is active and running on the site
  3. Check the installed version number
    In WordPress Admin > Plugins, click on the plugin name or view its details to read the Version number displayed
    Affected if the version displayed is 6.3.1 or lower (anything below 6.4.0)
  4. Inspect plugin files for nonce validation
    If you have file access, examine the plugin PHP files for form handling (especially in includes or classes folders). Look for the presence of 'wp_nonce_field', 'wp_verify_nonce', or 'check_admin_referer' functions in files handling state-changing actions like settings saves or transaction processing
    Affected if state-changing functions lack nonce validation checks

The site is affected if the Mercado Pago Payments for WooCommerce plugin is active and the installed version is below 6.4.0, allowing CSRF attacks on authenticated administrators.

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

Implement anti-CSRF tokens (nonce validation) on all state-changing operations and forms within the plugin, and update to a patched version if available from the vendor.

Recommended fix High confidence

Mercado Pago Payments for WooCommerce 6.4.0

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Mercado Pago Payments for WooCommerce' in the plugin list
  4. Click 'Update Now' if an update is available, or manually download version 6.4.0 or later from the WordPress plugin repository
  5. Verify the update completed successfully
  6. Test that payment processing through Mercado Pago continues to work correctly

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

Fix this in Mercado Pago Payments For Woocommerce Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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