dbcve.org
Zen CartApplication

CVE-2024-5762

HIGH · 8.1 CVSS v3.1 Published 2024-08-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
High EPSS 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
Zen Cart findPluginAdminPage Local File Inclusion Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Zen Cart. Authentication is not required to exploit this vulnerability. The specific flaw exists within the findPluginAdminPage function. The issue results from the lack of proper validation of user-supplied data prior to passing it to a PHP include function. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the service account. Was ZDI-CAN-21408.

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

Zen Cart's findPluginAdminPage function contains a Local File Inclusion (LFI) vulnerability where user-supplied input is not validated before being passed to a PHP include() function. This allows unauthenticated attackers to include arbitrary files, which can be chained with other vulnerabilities to achieve Remote Code Execution in the context of the service account.

MitigationApply input validation and sanitization to all user-supplied parameters in findPluginAdminPage before use in include statements; consider using allowlists and avoiding dynamic file inclusion. Check vendor for patches.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Zen CartApplication
Affected:= 1.5.8a

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

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

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 Zen Cart installation exists
    Look for Zen Cart files in the web root directory. Check for admin/includes/application_top.php or includes/application_top.php files. Alternatively, check for zc_install directory or look for 'Zen Cart' string in page source of the storefront.
    Affected if Zen Cart is installed on the server
  2. Identify installed Zen Cart version
    Check the version file: /includes/version.php or /admin/includes/version.php. Look for a variable like $project_version_major, $project_version_minor, or $zc_version. Compare against 1.5.8a.
    Affected if Installed version is exactly 1.5.8a (this specific version is affected)
  3. Locate the vulnerable findPluginAdminPage function
    Search the codebase for 'function findPluginAdminPage' in PHP files, typically found in admin/includes/classes/class.pluginAdmin.php or similar admin class files. Verify the function exists and contains an include() statement using user input.
    Affected if The findPluginAdminPage function exists and uses include() with unsanitized parameters
  4. Check if admin directory is internet-facing
    Verify the /admin/ directory is accessible from the internet without authentication. Attempt to access the admin login page externally. Check web server configuration for the admin folder.
    Affected if The admin interface is accessible without authentication (unauthenticated attackers can reach the vulnerable function)
  5. Inspect the function for unsanitized input usage
    Review the findPluginAdminPage function code to confirm it uses parameters like $_GET or $_REQUEST directly in include() statements without validation (e.g., no realpath(), no basename(), no allowlist check).
    Affected if User-supplied parameters are passed directly to include() without validation

A user is affected if Zen Cart 1.5.8a is installed, the findPluginAdminPage function uses include() with unsanitized user input, and the admin interface is accessible to unauthenticated attackers.

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

Apply input validation and sanitization to all user-supplied parameters in findPluginAdminPage before use in include statements; consider using allowlists and avoiding dynamic file inclusion. Check vendor for patches.

Recommended fix Moderate confidence

Zen Cart 1.5.8b or later (recommended: 1.5.9)

  1. 1. Backup your current Zen Cart installation and database before making any changes.
  2. 2. Navigate to the official Zen Cart downloads page at docs.zen-cart.com or the official GitHub repository.
  3. 3. Download the latest stable version of Zen Cart (version 1.5.8b or later, currently 1.5.9 as of late 2024).
  4. 4. Extract the new version files and replace the existing Zen Cart installation files, preserving your custom configuration and template files.
  5. 5. Review and update any custom code or modifications that may have been made to core files.
  6. 6. Test the upgraded installation to ensure the findPluginAdminPage function now properly validates user input before file inclusion.
  7. 7. Verify that the local file inclusion vulnerability is remediated by confirming the fix in the findPluginAdminPage function validates and sanitizes all user-supplied parameters.
Caveat Minor: Review custom modifications to core files as they may need updates; test all functionality after upgrade

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

Fix this in Zen Cart Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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