Primakon Pi Portal 1.0.18 API endpoints responsible for retrieving object-specific or filtered data (e.g., user
Source GCVE Database
Not known to be exploited · CVSS 5.3 Medium.
Data as of 19 Nov 2026, 02:23 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 5.3 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 18 Nov 2026.
What to do
AI-suggested
Users should monitor vendor advisories for updates. Until a fix is provided, restrict access to the affected API endpoints where possible and implement additional access controls or validation at the application or network level to limit unauthorized data access.
Description
Primakon Pi Portal version 1.0.18 contains API endpoints that do not properly validate user authorization when retrieving object-specific or filtered data. This allows attackers to manipulate ID parameters or omit filters to access unauthorized user or project data, exposing sensitive personal and organizational information.