WordPress security by component
Mercado Pago payments for WooCommerce
Plugin description
Mercado Pago payments for WooCommerce adds Mercado Pago payment methods to WooCommerce checkout.
Mercado Pago payments for WooCommerce (woocommerce-mercadopago) is a WordPress plugin with 4 published CVE records in this archive. The latest tracked vulnerability was published Aug 06, 2026; the highest published CVSS base score is 6.5.
Plugin slug:
woocommerce-mercadopagoLatest vulnerability
CVE-2026-28180: Mercado Pago permits unauthenticated insecure direct object reference
Mercado Pago payments for WooCommerce 8.9.0 and earlier exposes an object-level operation without adequately verifying that the unauthenticated requester is authorized for the referenced object.
| Safe version |
|
||
|---|---|---|---|
| Aug 06, 2026 |
CVE-2026-28180
Mercado Pago permits unauthenticated insecure direct object reference
Mercado Pago payments for WooCommerce 8.9.0 and earlier exposes an object-level operation without adequately verifying that the unauthenticated requester is authorized for the referenced object.
|
8.9.1 |
CVE5.3
NVDPending
|
| May 06, 2026 |
CVE-2026-3208
Mercado Pago payments for WooCommerce: A security weakness
Mercado Pago payments for WooCommerce is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 8.7.11.
|
See mitigation notes |
CVE5.3
NVDPending
|
| Jul 20, 2024 |
CVE-2024-3934
Mercado Pago payments for WooCommerce: Unauthorized file download
Mercado Pago payments for WooCommerce is affected by unauthorized file download. Exploitation requires an authenticated subscriber account. A successful request can download a file that the caller should not be permitted to access.
|
See mitigation notes |
CVE6.5
NVDPending
|
| Mar 01, 2023 |
CVE-2022-45068
Woocommerce Mercadopago: Cross-site request forgery
Woocommerce Mercadopago is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
|
See mitigation notes |
CVE4.3
NVD8.8
|