CVE-2024-1260
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 · uneditedA vulnerability classified as critical has been found in Juanpao JPShop up to 1.5.02. This affects the function actionIndex of the file /api/controllers/admin/app/ComboController.php of the component API. The manipulation of the argument pic_url leads to unrestricted upload. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-252999.
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 JPShop application up to version 1.5.02 contains an unrestricted file upload vulnerability in the ComboController.php API endpoint (actionIndex function). The 'pic_url' parameter accepts file uploads without proper validation, allowing remote attackers to upload malicious files such as webshells and achieve remote code execution.
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<= 1.5.02CVSS 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 JPShop installation and versionLocate the JPShop application installation directory and check the version number in version files, configuration files, or the application metadata (such as a version.php, composer.json with version info, or an about/version page within the application)Affected if The installed version is 1.5.02 or any version lower than 1.5.02 (the application displays a version number at or below 1.5.02)
-
Locate the vulnerable ComboController.php fileSearch for the file ComboController.php within the application source code directory, typically found in a controllers or api directory structureAffected if The file ComboController.php exists in the application and contains an actionIndex function that handles file uploads via the pic_url parameter
-
Verify the file upload endpoint is accessibleCheck if the web server configuration allows access to the ComboController.php endpoint (typically accessed via a URL path like /combo/index or /api/combo/index)Affected if The endpoint is reachable over HTTP/HTTPS and accepts POST requests with a pic_url parameter
-
Inspect current uploaded files in the applicationExamine the upload directory configured for the application (look for directories named uploads, upload, files, or similar in the web root) and check for any suspicious file types such as .php, .phtml, .php5, .phar, or other executable extensionsAffected if There are unexpected PHP files or other executable scripts present in the upload directories that were not intentionally uploaded by administrators
-
Review web server access logs for upload activitySearch web server access logs (Apache access.log, Nginx access.log) for POST requests to the ComboController endpoint containing pic_url parameter or multipart form data to identify recent upload attemptsAffected if Logs show recent POST requests to the vulnerable endpoint with file uploads, especially requests containing suspicious file types
You are affected if your JPShop version is 1.5.02 or lower and the ComboController.php file with the actionIndex function is present and accessible, as this combination allows the unrestricted file upload vulnerability to be exploited.
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 dataImplement strict file upload validation including whitelist of allowed file extensions, MIME type verification, file content magic byte inspection, and store uploads outside the web root or with non-executable permissions.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-1260 — 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-1260 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