CVE-2025-50693VulnerabilityPublished 24 Jun 2025

CVE-2025-50693: n/a

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Organizations should immediately audit access control mechanisms within the PHPGurukul Online DJ Booking Management System, focusing on the odms/request-details.php endpoint. Specific mitigation steps include: 1) Implement strict server-side authorization checks to ensure users can only access booking requests associated with their accounts or roles. 2) Employ parameter validation and avoid direct use of user-supplied identifiers without verification. 3) Introduce object-level access control policies, possibly leveraging role-based access control (RBAC) or attribute-based access control (ABAC) models. 4) Monitor logs for unusual access patterns to booking request details that could indicate exploitation attempts. 5) If possible, isolate the booking management system behind additional authentication layers or VPN access to reduce exposure. 6) Engage with the software vendor or community to obtain patches or updates addressing this vulnerability. 7) Educate users about the risks of sharing credentials and encourage strong authentication practices. 8) Conduct penetration testing focused on IDOR and other access control weaknesses to identify and remediate similar issues proactively.

Description

PHPGurukul Online DJ Booking Management System 2.0 is vulnerable to Insecure Direct Object Reference (IDOR) in odms/request-details.php.

Impact

For European organizations using the PHPGurukul Online DJ Booking Management System 2.0, this vulnerability could lead to unauthorized disclosure of sensitive booking and client information, undermining confidentiality. This could result in privacy violations, reputational damage, and potential regulatory non-compliance, especially under GDPR requirements for protecting personal data. Integrity risks exist if attackers can modify booking details, potentially disrupting business operations or causing financial loss. Availability impact is likely limited unless the vulnerability is chained with other exploits to cause denial of service. Given the niche nature of the software (DJ booking management), the overall impact is moderate but significant for affected entities, particularly event management companies, entertainment venues, or freelance DJs operating within Europe. The exposure of client data could also facilitate further targeted attacks such as phishing or social engineering. Since no known exploits are currently reported, the immediate risk is moderate, but the vulnerability should be addressed promptly to prevent future exploitation.

References

github.com/blackm4c/cve/blob/master/phpgurukul/odms/idor/README.md (opens in a new tab)

Community reviews

Loading reviews…