CVE-2025-65647VulnerabilityPublished 25 Nov 2025

CVE-2025-65647: n/a

Source CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.3Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 15% 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:L/I:N/A:N

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

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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Nov 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

1. Implement strict access control checks on the 'oid' parameter to ensure users can only access their own order information. 2. Enforce server-side authorization validation before returning any order-related data. 3. Conduct code reviews and penetration testing focusing on IDOR vulnerabilities in all object reference parameters. 4. If possible, apply patches or updates from PHPGURUKUL once available; in the meantime, consider temporary workarounds such as session-based order tracking. 5. Log and monitor access to order tracking endpoints to detect unusual access patterns or attempts to enumerate order IDs. 6. Educate developers on secure coding practices related to object references and authorization. 7. Review and update privacy policies and incident response plans to address potential data disclosure incidents. 8. Restrict API or web interface access to authenticated and authorized users only, minimizing exposure.

Description

CVE-2025-65647 is an Insecure Direct Object Reference (IDOR) vulnerability in the Track order function of PHPGURUKUL Online Shopping Portal 2.1. It allows an attacker with limited privileges to disclose information by manipulating the 'oid' parameter without requiring user interaction. The vulnerability has a medium severity with a CVSS score of 4.3, impacting confidentiality but not integrity or availability. No known exploits are currently reported in the wild. European organizations using this specific e-commerce platform could be at risk of unauthorized data exposure. Mitigation involves implementing proper access control checks on the 'oid' parameter and validating user permissions before disclosing order information. Countries with higher e-commerce adoption and usage of PHPGURUKUL products, such as Germany, France, and the UK, are more likely to be affected. Given the medium severity and limited scope, organizations should prioritize patching and access control improvements to prevent potential data leaks.

Impact

For European organizations using PHPGURUKUL Online Shopping Portal 2.1, this vulnerability could lead to unauthorized disclosure of customer order information, violating data privacy regulations such as GDPR. Exposure of order details may include personally identifiable information (PII), order contents, and transaction history, which could be leveraged for fraud, social engineering, or reputational damage. Although the vulnerability does not allow modification or deletion of data, the confidentiality breach alone can have significant compliance and trust implications. The medium severity reflects limited impact scope but notable risk due to ease of exploitation by authenticated users. Retailers and e-commerce businesses in Europe relying on this platform are particularly at risk, especially those handling large volumes of customer data. The absence of known exploits reduces immediate risk but does not eliminate the potential for future attacks. Organizations failing to address this vulnerability may face regulatory penalties and loss of customer confidence.

Summary

CVE-2025-65647 identifies an Insecure Direct Object Reference (IDOR) vulnerability in the Track order function of the PHPGURUKUL Online Shopping Portal version 2.1. IDOR vulnerabilities occur when an application exposes internal implementation objects, such as database keys or file names, without proper authorization checks. In this case, the 'oid' parameter, presumably representing an order identifier, can be manipulated by an attacker to access information related to other orders. The vulnerability allows information disclosure, impacting confidentiality, but does not affect data integrity or system availability. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) indicates that the attack can be performed remotely over the network with low attack complexity, requires low privileges (authenticated user), and no user interaction. The vulnerability is classified under CWE-639, which relates to authorization bypass through improper access control on object references. No patches or known exploits are currently available, suggesting this is a newly published vulnerability. The lack of affected version details implies the need for organizations to verify their use of PHPGURUKUL Online Shopping Portal 2.1 or related versions. The vulnerability's exploitation could lead to unauthorized disclosure of order information, potentially exposing customer data and order details.

CWE-639Authorization Bypass Through User-Controlled Key (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #24OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Architecture and Design
For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
Architecture and Design · Implementation
Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
Architecture and Design
Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
OWASP Cheat Sheets
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.1.2 (opens in a new tab)
V4.2.1 (opens in a new tab)
V8.3.8 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 2 Dec 2025, 20:06 UTC

WeaknessesCWE-639

Technical details

References

Community reviews

Related threats