dbcve.org
JpshopApplication · Juanpao

CVE-2024-1258

MEDIUM · 5.9 CVSS v3.1 Published 2024-02-06
Fix available
A fix is available. Upgrade to after 1.5.02 or later.
See remediation →
68/100
Remediation priority · Elevated
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 declared as problematic. Affected by this vulnerability is an unknown functionality of the file api/config/params.php of the component API. The manipulation of the argument JWT_KEY_ADMIN leads to use of hard-coded cryptographic key . The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The identifier VDB-252997 was 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

The JPShop application uses a hardcoded cryptographic key (JWT_KEY_ADMIN) in the API configuration file api/config/params.php for JWT token generation/validation. This allows attackers who discover the key to forge administrative JWT tokens and gain unauthorized access to the API.

MitigationReplace the hardcoded JWT_KEY_ADMIN value with a dynamically-generated key stored securely (e.g., environment variables, secrets management system) and implement key rotation. Regenerate all existing admin tokens after remediation.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Check JPShop version
    Locate the version information for your JPShop installation (commonly in composer.json, a version config file, or API response headers).
    Affected if The installed version is 1.5.02 or lower.
  2. Verify api/config/params.php exists
    Confirm the file api/config/params.php is present in your JPShop installation directory.
    Affected if The file api/config/params.php exists in the application root.
  3. Inspect for JWT_KEY_ADMIN definition
    Open api/config/params.php and search for a variable or constant named JWT_KEY_ADMIN.
    Affected if JWT_KEY_ADMIN is defined in api/config/params.php with a hardcoded value.
  4. Determine if key is hardcoded
    Examine how JWT_KEY_ADMIN is assigned its value. Check if it is set to a static string literal (e.g., 'somekey123') rather than being retrieved dynamically from environment variables (e.g., getenv('JWT_KEY_ADMIN')).
    Affected if JWT_KEY_ADMIN is assigned a static string value directly in the code.

You are affected if your JPShop version is 1.5.02 or lower AND the api/config/params.php file contains a hardcoded JWT_KEY_ADMIN string value.

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

Replace the hardcoded JWT_KEY_ADMIN value with a dynamically-generated key stored securely (e.g., environment variables, secrets management system) and implement key rotation. Regenerate all existing admin tokens after remediation.

Recommended fix Moderate confidence
  1. 1. Locate the file api/config/params.php in the JPShop installation
  2. 2. Identify the hardcoded JWT_KEY_ADMIN value in the configuration
  3. 3. Replace the hardcoded JWT_KEY_ADMIN value with a dynamically generated cryptographic key or a reference to an environment variable
  4. 4. Ensure the new key is unique, sufficiently long (recommended 256+ bits), and stored securely outside the web root
  5. 5. If using an environment variable, update the application to read JWT_KEY_ADMIN from the environment at runtime
  6. 6. Restart the application services to apply the new configuration
  7. 7. Verify that API authentication still functions correctly with the new key

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

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