CVE-2024-33836
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 · uneditedIn the module "JA Marketplace" (jamarketplace) up to version 9.0.1 from JA Module for PrestaShop, a guest can upload files with extensions .php. In version 6.X, the method `JmarketplaceproductModuleFrontController::init()` and in version 8.X, the method `JmarketplaceSellerproductModuleFrontController::init()` allow upload of .php files, which will lead to a critical vulnerability.
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 confidenceThe JA Marketplace PrestaShop module allows unauthenticated guest users to upload arbitrary .php files through vulnerable controller methods (JmarketplaceproductModuleFrontController::init() in v6.X and JmarketplaceSellerproductModuleFrontController::init() in v8.X). This missing file type validation permits remote code execution by uploading malicious PHP scripts.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify JA Marketplace module versionLocate the module's main file (typically ja_marketplace.php) in modules/ja_marketplace/ and open it to find the version number defined in the $version variable, or check via PrestaShop back office in Modules > Module Manager > JA MarketplaceAffected if Version is 6.X or 8.X (any subversion)
-
Determine the vulnerable controller in useInspect the modules/ja_marketplace/controllers/front/ directory - if JmarketplaceproductModuleFrontController.php exists, the v6.X vulnerability path is present; if JmarketplaceSellerproductModuleFrontController.php exists, the v8.X vulnerability path is presentAffected if Either JmarketplaceproductModuleFrontController.php (v6.X) or JmarketplaceSellerproductModuleFrontController.php (v8.X) controller file exists in the controllers/front folder
-
Check module upload directory accessibilityExamine the modules/ja_marketplace/uploads/ directory (or similar upload path configured in the module) and verify it is web-accessible and permits file uploads without validationAffected if The module's upload directory exists and is writable by the web server user
-
Inspect upload directory for suspicious PHP filesList all files in the module's upload directory and check for any .php files with names that do not match expected module behavior (e.g., shell.php, payload.php, or other unrecognized PHP files)Affected if Any .php files are present in the upload directory that were not placed there by the module itself
If the JA Marketplace module version is 6.X or 8.X and the corresponding vulnerable controller is present, the environment is vulnerable to unauthenticated arbitrary file upload and potential remote code execution.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate JA Marketplace module to version 9.0.2 or later which contains the patched file upload validation. If immediate update is not possible, disable the affected controller methods or implement web application firewall (WAF) rules to block .php file uploads to the module's upload directory.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2024-33836 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-33836 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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