Mercado Pago payments for WooCommerce - Path Traversal (CVE-2024-3934)

CVE-2024-3934

Vulnerability CVE-2024-3934 PLUGIN mercado-pago-payments-for-woocommerce MEDIUM

The Mercado Pago payments for WooCommerce plugin for WordPress is vulnerable to Path Traversal in versions 7.3.0 to 7.5.1 via the mercadopagoDownloadLog function. This makes it possible for authenticated attackers, with subscriber-level access and above, to download and read the contents of arbitrary files on the server, which can contain sensitive information. The arbitrary file download was patched in 7.5.1, while the missing authorization was corrected in version 7.6.2.

CVE-2024-3934

MEDIUM CVSS 6.5 Published 2024-07-20 Updated 2026-06-17

AI Risk Elevated (70/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P3 Priority

Severity Band MEDIUM

CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected Components 2

Reference Links 4

AI Risk Engine Elevated (70/100)

Exploitability High

Active Exploitation No strong signal

Published Exploit Status No public exploit references

Threat Timeline

2024-07-20 CVE published and first recorded in the threat feed.
2026-06-17 Record updated with latest vulnerability metadata.
2026-04-09 AI technical context refreshed for mitigation and impact guidance.
Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 167 days ago

AI enriched 167 days ago (2026-04-09 10:10 UTC)

Technical Summary

Potential Impact

Severity is MEDIUM (CVSS 6.5). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on remote code execution potential, low-bar exploit prerequisites.

Primary risk drivers: remote code execution potential, low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Mercado Pago payments for WooCommerce PLUGIN · mercado-pago-payments-for-woocommerce Affected range not specified Fixed in: 7.5.1

Woocommerce Mercadopago PLUGIN · woocommerce-mercadopago Affected range not specified Fixed in: 7.5.1

References

What to do about this

Patch on your next cycle Worth fixing, but not ahead of other work.

Fix it

Update Mercado Pago payments for WooCommerce to 7.5.1 or later.

That is the complete fix. Everything below is what protects you in the meantime.

Cannot update today? Request / payload inspection (WAF) in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.

Inspect request parameters and bodies for injection, traversal and file-inclusion payloads, and refuse the request rather than logging it.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs Mercado Pago payments for WooCommerce, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs Mercado Pago payments for WooCommerce. Versions below 7.5.1 are vulnerable; that release and later are not.

How do I fix it?

Update Mercado Pago payments for WooCommerce to version 7.5.1 or later. That is the complete fix. Until you can update, Request / payload inspection (WAF) in Hack Halt ProSecure contains this class of attack at the request layer.

What can an attacker actually do?

This is a Path Traversal flaw. An attacker who exploits it can read files outside the intended directory, including wp-config.php.