dbcve.org
JpshopApplication · Juanpao

CVE-2024-1259

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 was found in Juanpao JPShop up to 1.5.02. It has been rated as critical. Affected by this issue is some unknown functionality of the file /api/controllers/admin/app/AppController.php of the component API. The manipulation of the argument app_pic_url leads to unrestricted upload. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. VDB-252998 is the identifier assigned to this 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 confidence

Juanpao JPShop up to version 1.5.02 contains an unrestricted file upload vulnerability in the API endpoint /api/controllers/admin/app/AppController.php. The app_pic_url parameter is not properly validated, allowing remote attackers to upload arbitrary files including malicious scripts. The vulnerability is remotely exploitable and public exploits are available.

MitigationImplement strict file type validation (allowlist approach), validate file extensions and MIME types, store uploaded files outside the webroot or rename them, and disable script execution in the upload directory. Restrict upload functionality to authenticated administrators only.

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 installation directory and check version.php, composer.json, or any version file within the application root. Common paths include /var/www/html/jpshop or similar web root locations.
    Affected if The installed version is 1.5.02 or any version lower than 1.5.02.
  2. Verify vulnerable file exists
    Check if the file /api/controllers/admin/app/AppController.php exists in the JPShop installation directory. Use a file search command like 'find' or inspect the directory structure via FTP or file manager.
    Affected if The file AppController.php exists in the path /api/controllers/admin/app/ within the application.
  3. Inspect the app_pic_url parameter handling
    Examine the AppController.php file and locate the code handling the app_pic_url parameter. Look for any file upload or validation logic applied to this parameter.
    Affected if The app_pic_url parameter accepts file input without proper validation or sanitization.
  4. Check upload directory configuration
    Identify where uploaded files are stored (check upload directories, assets folders, or media directories). Verify if these directories are within the webroot and if they allow script execution.
    Affected if Uploaded files are stored inside the webroot and script execution is not disabled in that directory.
  5. Assess endpoint access control
    Test accessing the /api/controllers/admin/app/AppController.php endpoint without authentication. Check if the upload functionality is accessible to unauthenticated users.
    Affected if The upload endpoint is accessible without authentication or proper authorization checks.

You are affected if your JPShop version is 1.5.02 or lower, the vulnerable AppController.php file exists, and the upload functionality is exposed without proper validation or access controls.

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 type validation (allowlist approach), validate file extensions and MIME types, store uploaded files outside the webroot or rename them, and disable script execution in the upload directory. Restrict upload functionality to authenticated administrators only.

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