# CVE-2026-3208: Missing authorization in Mercado Pago payments for WooCommerce

> Unauthenticated attackers can retrieve PIX payment QR code images for arbitrary orders, exposing sensitive merchant and transaction data.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 May 2026
- **Updated:** 6 May 2026
- **Also known as:** GHSA-cfhj-895c-686j

## What is CVE-2026-3208?

CVE-2026-3208 is a medium-severity missing authorization vulnerability in mercadopago Mercado Pago payments for WooCommerce, published on 6 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Mercado Pago payments for WooCommerce plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'mp_pix_image' WooCommerce API endpoint in all versions up to, and including, 8.7.11. This makes it possible for unauthenticated attackers to retrieve PIX payment QR code images for arbitrary orders. PIX QR codes contain sensitive merchant information including PIX keys (which may be CPF/CNPJ personal identifiers), transaction amounts, merchant name and city, and MercadoPago transaction references.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-3208?


## How do I fix CVE-2026-3208?

No fix has been published for CVE-2026-3208 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-3208 being exploited?

There is no known exploitation of CVE-2026-3208 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3208 and fix it if it is affected.

What it is: CVE-2026-3208 is a medium-severity missing authorization vulnerability in mercadopago Mercado Pago payments for WooCommerce, published on 6 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-3208 in the wild and no public exploit code.

Affected product: mercadopago Mercado Pago payments for WooCommerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-3208/ (Markdown: https://insights.sbomify.com/CVE-2026-3208/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3208
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3208
- OSV: https://osv.dev/vulnerability/CVE-2026-3208

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-3208/
Summaries are generated and may contain mistakes; the official description above is the record.