CVE-2025-64062: Primakon · Improper Authorization
Affects PrimakonSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% 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:H/A:HExploitation 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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubn3k7ar91/Primakonpkg:github/n3k7ar91/PrimakonOther threats | Affected
| 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-2025-64062, organizations should implement strict server-side validation to ensure that the email parameter in the /api/V2/pp_users endpoint matches the authenticated user's session identity. The application logic must reject any requests where the email parameter does not correspond to the session or is missing. Specifically, the system should never default to the first user or any privileged account when the email parameter is blank or invalid. Access control checks must be enforced at the API level to prevent unauthorized data access and privilege escalation. Organizations should audit their current deployments of Primakon Pi Portal to identify affected versions and restrict access to the vulnerable API endpoint through network segmentation or firewall rules until a patch is available. Monitoring and logging of API requests for unusual email parameter values or access patterns can help detect exploitation attempts. Where possible, multi-factor authentication should be enforced for administrative accounts to reduce the risk of compromise. Finally, organizations should engage with the vendor or community to obtain patches or updates addressing this vulnerability and apply them promptly once available.
Description
The Primakon Pi Portal 1.0.18 /api/V2/pp_users?email endpoint is used for user data filtering but lacks proper server-side validation against the authenticated session. By manipulating the email parameter to an arbitrary value (e.g., otheruser@user.com), an attacker can assume the session and gain full access to the target user's data and privileges. Also, if the email parameter is left blank, the application defaults to the first user in the list, who is typically the application administrator, resulting in an immediate Privilege Escalation to the highest level.