CyberSecBulletin

Primakon vulnerabilities

We track 5 vulnerabilities in Primakon products. 5 are rated high or critical, and none are known to be exploited. The most recent was published on November 25, 2025.

5vulnerabilities
1critical
4high
0exploited
9.0average CVSS score

Latest Primakon vulnerabilities

  • 8.8 High severity

    Project Contract Management: Improper Authorization

    CVE-2025-64065Primakon

    The Primakon Pi Portal 1.0.18 API /api/V2/pp_udfv_admin endpoint, fails to perform necessary server-side validation. The administrative LoginAs or user impersonation feature is vulnerable to a access control failure. This flaw allows any authenticated low-priv

  • 8.8 High severity

    Project Contract Management: Improper Access Control

    CVE-2025-64064Primakon

    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 permissi

  • 9.8 Critical severity

    Project Contract Management: Improper Authorization

    CVE-2025-64063Primakon

    Primakon Pi Portal 1.0.18 API endpoints fail to enforce sufficient authorization checks when processing requests. Specifically, a standard user can exploit this flaw by sending direct HTTP requests to administrative endpoints, bypassing the UI restrictions. Th

  • 8.6 High severity

    Project Contract Management: Improper Access Control

    CVE-2025-64066Primakon

    Primakon Pi Portal 1.0.18 REST /api/v2/user/register endpoint suffers from a Broken Access Control vulnerability. The endpoint fails to implement any authorization checks, allowing unauthenticated attackers to perform POST requests to register new user account

  • 8.8 High severity

    Project Contract Management: Improper Authorization

    CVE-2025-64062Primakon

    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., [email protected]), an at