dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-3934

MEDIUM · 6.5 CVSS v3.1 Published 2024-07-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
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.

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 · high confidence

The Mercado Pago payments for WooCommerce plugin contains a path traversal vulnerability in the mercadopagoDownloadLog function affecting versions 7.3.0 through 7.5.1. Authenticated attackers with subscriber-level access or higher can manipulate file paths to read arbitrary files on the server, potentially exposing sensitive configuration or system files.

MitigationUpdate the plugin to version 7.6.2 or later, which patches both the arbitrary file download (7.5.1) and the missing authorization check (7.6.2). Review access controls and monitor for suspicious log download requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 Mercado Pago plugin is installed
    Navigate to Plugins > Instored Plugins in WordPress admin, or check the plugin directory for the mercadopago-payments-for-woocommerce folder. Look for the plugin version number in the plugin description.
    Affected if The Mercado Pago payments for WooCommerce plugin is installed and the version falls between 7.3.0 and 7.5.1 inclusive.
  2. Confirm the installed version number
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Mercado Pago payments for WooCommerce'. Read the version number displayed below the plugin name. Alternatively, check the main plugin PHP file for the version constant.
    Affected if The installed version is 7.3.0, 7.4.0, 7.4.1, 7.5.0, or 7.5.1.
  3. Check for the mercadopagoDownloadLog function
    Search the plugin files (typically in includes/class-mercadopago.php or similar) for the function named 'mercadopagoDownloadLog' or 'downloadLog'. Inspect the function code to see if it uses user input (like a filename parameter) without proper sanitization before file operations.
    Affected if The mercadopagoDownloadLog function exists in the plugin and processes file path parameters without validating they are within an allowed directory.
  4. Inspect access control on the log download feature
    Examine the function's capability check or nonce verification. Look for checks like 'current_user_can' or 'wp_verify_nonce' immediately before the file download logic. Determine what minimum user role can access this endpoint.
    Affected if The function allows access to subscriber-level users (or any authenticated user) without proper authorization verification, or lacks capability checks entirely.
  5. Review access logs for suspicious log download requests
    Check server access logs and WordPress audit logs for requests to the log download endpoint (typically wp-admin/admin-ajax.php?action=mercadopago_download_log or similar). Look for patterns like '../' path traversal sequences in the request parameters.
    Affected if Log entries show requests to the log download function with manipulated path parameters containing ../ sequences, or requests from low-privilege users accessing this functionality.

Your environment is affected if the Mercado Pago payments for WooCommerce plugin version is 7.3.0 through 7.5.1 and the mercadopagoDownloadLog function is accessible to authenticated users with subscriber-level permissions or higher.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 7.6.2 or later, which patches both the arbitrary file download (7.5.1) and the missing authorization check (7.6.2). Review access controls and monitor for suspicious log download requests.

Recommended fix High confidence

7.6.2 or latest available version

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find the 'Mercado Pago payments for WooCommerce' plugin
  4. Click 'Update now' if an update is available, or manually download version 7.6.2 or later from wordpress.org/plugins/woocommerce-mercadopago/
  5. Verify the update completes successfully
  6. Confirm the updated version is 7.6.2 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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