dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-34990

CRITICAL · 10.0 CVSS v3.1 Published 2024-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
In the module "Help Desk - Customer Support Management System" (helpdesk) up to version 2.4.0 from FME Modules for PrestaShop, a customer can upload .php files. Methods `HelpdeskHelpdeskModuleFrontController::submitTicket()` and `HelpdeskHelpdeskModuleFrontController::replyTicket()` allow upload of .php files on a predictable path for connected customers.

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 Help Desk module for PrestaShop fails to validate uploaded file types in the submitTicket() and replyTicket() controller methods. Authenticated customers can upload arbitrary .php files which are stored in a predictable path, enabling remote code execution.

MitigationImmediately disable the module or block public access to the affected endpoints. Implement strict allowlist-based file validation rejecting .php and other executable extensions, and store uploads outside the webroot or with non-executable names.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Verify Help Desk module is installed
    List installed PrestaShop modules and look for 'helpdesk' or 'hd' named module, or inspect the /modules/ directory for helpdesk-related folders
    Affected if The Help Desk module is present in the PrestaShop modules directory
  2. Determine installed Help Desk module version
    Open the module's main PHP file (usually in /modules/helpdesk/ or similar naming) and read the version defined in the module descriptor or config file
    Affected if The version is unpatched and falls within the vulnerable range (confirm with vendor release notes)
  3. Identify upload directories used by the module
    Search the module code for upload handling in submitTicket() and replyTicket() methods, look for 'move_uploaded_file', 'copy', or file path definitions; check /img/tmp/ or /upload/ directories
    Affected if Predictable upload directories exist and are accessible via web
  4. Scan upload directories for unauthorized .php files
    List all files in the module's upload directories (e.g., /img/tmp/, /upload/) and check for .php extensions that should not be present
    Affected if Any .php files are found in publicly accessible upload directories
  5. Verify file type validation is enforced
    Review the module's PHP code for submitTicket() and replyTicket() methods; look for file extension validation or MIME type checking that rejects .php files
    Affected if No file extension or MIME type validation exists, or validation can be bypassed

If the Help Desk module is installed without recent security patches and allows file uploads through submitTicket() or replyTicket() methods without proper validation, the environment is likely affected.

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

Immediately disable the module or block public access to the affected endpoints. Implement strict allowlist-based file validation rejecting .php and other executable extensions, and store uploads outside the webroot or with non-executable names.

Recommended fix Moderate confidence

Upgrade to helpdesk module version 2.4.1 or later

  1. 1. Log in to the PrestaShop admin dashboard
  2. 2. Navigate to the Modules section and locate the 'Help Desk - Customer Support Management System' (helpdesk) module
  3. 3. Check the current installed version - if it is 2.4.0 or earlier, an update is required
  4. 4. Check for an available module update through the PrestaShop marketplace or contact FME Modules directly
  5. 5. Before upgrading, backup the entire PrestaShop installation including the database
  6. 6. Install the updated version of the helpdesk module (version 2.4.1 or later)
  7. 7. Verify the fix by attempting to upload a non-PHP file through the submitTicket() and replyTicket() forms
  8. 8. Confirm that .php file uploads are now blocked and proper file type validation is in place
Caveat Review module release notes for any changes to ticket submission workflows or API compatibility

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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