CVE-2025-64064: Primakon · Improper Access Control
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
- Immediately restrict access to the /api/v2/pp_users endpoint to only trusted and necessary users, ideally limiting it to administrators via network segmentation or firewall rules.
- Implement strict monitoring and alerting for any changes to user privilege levels, especially modifications to PP_SECURITY_PROFILE_ID.
- Enforce multi-factor authentication (MFA) for all user accounts to reduce the risk of compromised credentials being used to exploit this vulnerability.
- Conduct a thorough audit of existing user privileges to identify any unauthorized escalations and revert them.
- Engage with Primakon to obtain and apply official patches or updates addressing this vulnerability as soon as they become available.
- If patching is delayed, consider deploying a Web Application Firewall (WAF) with custom rules to detect and block PATCH requests attempting to modify PP_SECURITY_PROFILE_ID.
- Educate users about the importance of reporting suspicious account behavior promptly.
- Review and tighten API authentication and authorization mechanisms to prevent similar flaws in the future.
Description
Primakon Pi Portal 1.0.18 /api/v2/pp_users endpoint fails to adequately check user permissions before processing a PATCH request to modify the PP_SECURITY_PROFILE_ID. Because of weak access controls any low level user can use this API and change their permission to Administrator by using PP_SECURITY_PROFILE_ID=2 inside body of request and escalate privileges.