Skip to main content
VulnerabilityPublished Updated

CVE-2024-50651: java_shop · Insecure Direct Object Reference

Affects java_shopSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubyllxx03/java_shoppkg:github/yllxx03/java_shopOther threatsAffected
  • =1.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-50651, organizations should implement strict access control checks on all user-related parameters, especially the ID parameter used to fetch user data. This includes validating that the requesting user is authorized to access the requested resource before returning any sensitive information. Employ role-based access control (RBAC) or attribute-based access control (ABAC) mechanisms to enforce least privilege principles. Conduct thorough code reviews and penetration testing focused on access control logic. If patches become available, apply them promptly. In the absence of patches, deploy web application firewalls (WAFs) with custom rules to detect and block suspicious parameter tampering. Monitor logs for unusual access patterns involving user ID modifications. Educate developers on secure coding practices related to authorization and parameter validation. Additionally, consider implementing rate limiting and anomaly detection to reduce the risk of automated exploitation attempts.

Description

java_shop 1.0 is vulnerable to Incorrect Access Control, which allows attackers to obtain sensitive information of users with different IDs by modifying the ID parameter.

References

Community reviews

Loading reviews…