dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-38740

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/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
Missing Authorization vulnerability in Packlink Shipping S.L. Packlink PRO shipping module allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Packlink PRO shipping module: from n/a through 3.4.6.

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 Packlink PRO shipping module contains a missing authorization vulnerability where the application fails to properly enforce access control checks on certain functionality. This allows authenticated users or attackers to exploit incorrectly configured access control security levels to perform actions they should not be permitted to perform. The vulnerability exists in versions through 3.4.6 of the module.

MitigationImplement proper authorization checks throughout the module, ensuring all sensitive operations validate user permissions before execution. Review and correct access control configurations to enforce the principle of least privilege.

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
None
Integrity
Low
Availability
Low

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

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. Confirm Packlink PRO module is installed
    Locate the Packlink PRO shipping module files in your e-commerce platform's module directory. Common paths include /wp-content/plugins/ for WordPress/WooCommerce, /modules/ for PrestaShop, or the equivalent module folder for your platform.
    Affected if The Packlink PRO shipping module is present on the system
  2. Identify the installed module version
    Open the main module file (such as packlink.php, index.php, or a config file within the module folder) and locate the version declaration or metadata. This is typically found in file headers, a dedicated version file, or the module's configuration panel in the admin interface.
    Affected if The version number cannot be determined or is not visible
  3. Compare version against affected range
    Compare your installed version to the affected range: versions 3.4.6 and earlier are affected by this vulnerability. If your version is 3.4.6 or lower, or if you cannot determine the exact version, treat the module as potentially affected.
    Affected if The installed version is 3.4.6 or lower, or the version cannot be verified
  4. Verify access control configuration
    Review the module's access control settings or configuration files. Check whether sensitive administrative functions, API endpoints, or backend operations within the module enforce proper authorization checks. Look for configuration options related to user roles, permissions, or access levels.
    Affected if Access control settings are misconfigured, missing, or allow unauthorized access to sensitive functionality
  5. Test for unauthorized access to sensitive functions
    If you have access to the module's administrative interface, verify whether lower-privileged users can access functions that should be restricted to administrators or higher roles. Alternatively, review server logs for unexpected access patterns to module endpoints.
    Affected if Users with insufficient permissions can access or execute actions they should not be permitted to perform

Your environment is affected if the Packlink PRO shipping module is installed with version 3.4.6 or lower, or if the version cannot be verified, and sensitive module functions lack proper authorization enforcement.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks throughout the module, ensuring all sensitive operations validate user permissions before execution. Review and correct access control configurations to enforce the principle of least privilege.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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