dbcve.org
JpshopApplication · Juanpao

CVE-2024-1261

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-06
Fix available
A fix is available. Upgrade to after 1.5.02 or later.
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
A vulnerability classified as critical was found in Juanpao JPShop up to 1.5.02. This vulnerability affects the function actionIndex of the file /api/controllers/merchant/app/ComboController.php of the component API. The manipulation of the argument pic_url leads to unrestricted upload. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-253000.

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

Unrestricted file upload vulnerability in JPShop's ComboController.php API. The actionIndex function accepts a pic_url parameter without validating the file type or content, allowing remote attackers to upload malicious files (e.g., web shells) directly to the server. With CVSS 9.8 and network-exploitable attack vector, this can lead to complete system compromise.

MitigationImplement strict file validation: whitelist allowed extensions/MIME types, validate file content (magic bytes), store uploads outside webroot or rename files, and add authentication checks to the API endpoint.

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
JpshopApplication
Affected:<= 1.5.02

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify JPShop installation and version
    Locate the JPShop application on the server. Check for version information in configuration files, composer.json, or application metadata typically found in the application root or version-specific files.
    Affected if The installed JPShop version is 1.5.02 or lower (the version number is not explicitly available but the affected range is <= 1.5.02)
  2. Locate ComboController.php file
    Search for the file ComboController.php in the application source code, typically found in the controllers directory under the JPSHOP or similar application path.
    Affected if The file exists in the application, indicating the vulnerable component is present
  3. Verify pic_url parameter handling in actionIndex
    Examine the actionIndex function within ComboController.php. Review the code to confirm that a pic_url parameter is accepted and processed without file type validation.
    Affected if The actionIndex function accepts and processes a pic_url parameter without validating the file type or content
  4. Confirm lack of file validation logic
    Review the code handling the pic_url parameter in ComboController.php. Look for absence of extension whitelisting, MIME type checking, or magic byte validation before file processing.
    Affected if No file type/content validation is performed on uploads before saving files to the server
  5. Check API endpoint exposure
    Determine if the ComboController API endpoint is accessible without authentication. Review routing configuration and access controls for the endpoint.
    Affected if The endpoint is accessible over the network without authentication, allowing external attackers to exploit the vulnerability

A system is affected if it runs Juanpao JPShop version 1.5.02 or lower with the ComboController.php file present and its actionIndex function handling pic_url parameter without file validation, and the API endpoint is network-accessible.

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
Upgrade available Upgrade to a release after 1.5.02
Interim mitigation

Implement strict file validation: whitelist allowed extensions/MIME types, validate file content (magic bytes), store uploads outside webroot or rename files, and add authentication checks to the API endpoint.

Fix this in Jpshop 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 the upgrade done

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-1261 — 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-1261 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