VulnerabilityPublished 25 Nov 2025

CVE-2025-64067: Insecure Direct Object Reference

Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.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:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
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: 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: 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 26 Oct 2026.

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 or the CVSS exploit maturity 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 implement strict server-side authorization checks to ensure that API requests are validated against the requesting user's permissions before returning any data. This includes verifying that the user is authorized to access the specific object identified by any ID parameters and enforcing filtering parameters to prevent unfiltered data retrieval. Input validation should be enhanced to reject requests with manipulated or missing filter parameters. Conduct a thorough code review of all API endpoints handling sensitive data to identify and remediate similar authorization flaws. Employ logging and monitoring to detect unusual access patterns or large data retrievals indicative of exploitation attempts. If possible, restrict API access to trusted networks or authenticated users until patches or fixes are available. Engage with the vendor for official patches or updates and apply them promptly once released. Additionally, conduct regular security assessments and penetration testing focused on API authorization controls to prevent recurrence.

Description

CVE-2025-64067 is a medium severity vulnerability affecting Primakon Pi Portal 1.0.18 API endpoints. The flaw arises from insufficient server-side authorization validation, allowing attackers to manipulate ID parameters or omit filters to access unauthorized user or project data. Exploitation does not require authentication or user interaction and can lead to unauthorized disclosure of sensitive personal and organizational information. Although no known exploits are currently in the wild, the vulnerability poses a significant privacy risk. European organizations using this software should prioritize mitigation to prevent data exposure. The vulnerability is rated with a CVSS score of 5.3, reflecting its moderate impact primarily on confidentiality. Mitigation involves implementing strict server-side authorization checks and validating all input parameters.

Impact

For European organizations, the unauthorized exposure of sensitive personal and organizational data can have significant consequences. This includes violations of the EU General Data Protection Regulation (GDPR), which mandates strict controls over personal data access and disclosure. Data leakage could lead to regulatory fines, legal liabilities, and loss of customer trust. Organizations in sectors such as finance, healthcare, government, and critical infrastructure that rely on Primakon Pi Portal for managing sensitive data are particularly at risk. The vulnerability could facilitate insider threats or external attackers gaining access to confidential information, potentially enabling further attacks such as social engineering or targeted phishing. Although the vulnerability does not impact system integrity or availability, the confidentiality breach alone can disrupt business operations and damage organizational reputation. Given the ease of exploitation without authentication, attackers can remotely access data, increasing the threat surface for European entities using this software.

Summary

CVE-2025-64067 identifies a security vulnerability in Primakon Pi Portal version 1.0.18, specifically in its API endpoints responsible for retrieving object-specific or filtered data such as user profiles and project records. The core issue is the lack of sufficient server-side validation to verify that the requesting user is authorized to access the requested resource. This results in two primary exploitation methods: first, direct ID manipulation or Insecure Direct Object Reference (IDOR), where an attacker alters an ID parameter (e.g., user_id or project_id) in the API request to access data belonging to other users; second, filter omission, where the attacker omits filtering parameters entirely, causing the API to return an unfiltered dataset containing all stored records across users. This vulnerability falls under CWE-639, which relates to authorization bypass through improper validation. The vulnerability does not require authentication or user interaction, making it remotely exploitable over the network with low attack complexity. The CVSS 3.1 base score is 5.3, indicating a medium severity primarily due to confidentiality impact without affecting integrity or availability. No patches or known exploits have been reported yet. The vulnerability exposes sensitive personal and organizational data, potentially leading to privacy violations, compliance issues, and reputational damage for affected organizations.

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