dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-13820

MEDIUM · 5.3 CVSS v3.1 Published 2025-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Melhor Envio plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.15.11 via the 'run' function, which uses a hardcoded hash. This makes it possible for unauthenticated attackers to extract sensitive data including environment information, plugin tokens, shipping configurations, and limited vendor information.

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

The Melhor Envio WordPress plugin versions up to 2.15.11 contain a hardcoded hash in the 'run' function that enables unauthenticated attackers to bypass authentication and retrieve sensitive data including environment information, plugin tokens, shipping configurations, and limited vendor information.

MitigationUpdate to the latest version of the Melhor Envio plugin when available, rotate any exposed tokens or API credentials, and review access logs for suspicious activity targeting the affected endpoint.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Melhor Envio plugin is installed
    Access WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'Melhor Envio' in the list. Note the installed version displayed.
    Affected if Plugin is installed and version is 2.15.11 or lower
  2. Confirm plugin version number
    Check the plugin version in the plugin header comment by examining the main plugin file (typically wp-content/plugins/melhor-envio/melhor-envio.php) or via WordPress admin plugin page.
    Affected if Version is 2.15.11 or any version up to 2.15.11 inclusive
  3. Identify vulnerable endpoint
    Locate the 'run' function in the plugin files (search for function run() or public function run within the plugin directory). Determine if this function is hooked to a REST API route or direct access point without authentication checks.
    Affected if The 'run' function is exposed via an accessible endpoint without authentication requirements
  4. Inspect for hardcoded authentication hash
    Examine the 'run' function code in the plugin files. Search for any hardcoded hash, token, or key used for authentication bypass within this function.
    Affected if A hardcoded hash is present in the 'run' function code enabling unauthenticated access

A user is affected if the Melhor Envio plugin version is 2.15.11 or lower and the 'run' function with its hardcoded hash is accessible without authentication.

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 to the latest version of the Melhor Envio plugin when available, rotate any exposed tokens or API credentials, and review access logs for suspicious activity targeting the affected endpoint.

Recommended fix Moderate confidence

Update to the latest version available in the WordPress plugin repository (version > 2.15.11)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Melhor Envio' plugin
  4. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org/plugins/melhor-envio and upload it
  5. Verify the updated version is greater than 2.15.11
  6. Test that the plugin functionality works correctly after the update

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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