dbcve.org
Project Contract ManagementApplication · Primakon

CVE-2025-64064

HIGH · 8.8 CVSS v3.1 Published 2025-11-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The /api/v2/pp_users endpoint in Primakon Pi Portal 1.0.18 lacks proper authorization validation on PATCH requests, allowing any authenticated user to modify their own PP_SECURITY_PROFILE_ID attribute. By setting PP_SECURITY_PROFILE_ID=2 in the request body, low-privilege users can escalate their account to Administrator level.

MitigationImplement role-based access control (RBAC) on the /api/v2/pp_users endpoint to enforce authorization checks, ensuring only users with Administrator privileges can modify PP_SECURITY_PROFILE_ID. Validate the caller's permissions before processing any security profile changes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Project Contract ManagementApplication
Affected:= 1.0.18

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed version of Primakon Project Contract Management
    Check your application software version or look for version metadata in the application (typically found in about pages, configuration files, or HTTP response headers)
    Affected if The version is 1.0.18 exactly
  2. Verify the /api/v2/pp_users endpoint is accessible
    Send a GET or HEAD request to https://[host]/api/v2/pp_users (or the appropriate base URL for your instance) and confirm the endpoint responds
    Affected if The endpoint returns a valid HTTP response (200, 401, 403, etc.) rather than a 404 - the endpoint exists and is reachable
  3. Test if PATCH requests can modify PP_SECURITY_PROFILE_ID without admin authorization
    As a low-privilege authenticated user, send a PATCH request to /api/v2/pp_users with a body containing PP_SECURITY_PROFILE_ID=2 (or PP_SECURITY_PROFILE_ID set to any value different from the user's current profile) and observe whether the change is accepted
    Affected if The PATCH request succeeds and the user's security profile is modified without the server rejecting the request due to insufficient privileges
  4. Review application logs for recent privilege escalation or profile changes
    Check server and application logs for entries related to PP_SECURITY_PROFILE_ID modifications on the /api/v2/pp_users endpoint, particularly from non-admin accounts
    Affected if Logs show PP_SECURITY_PROFILE_ID changes performed by users who should not have had permission to modify this attribute

You are affected if Primakon Project Contract Management version 1.0.18 is running and the /api/v2/pp_users endpoint accepts PATCH requests that allow any authenticated user to change their own PP_SECURITY_PROFILE_ID to escalate privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement role-based access control (RBAC) on the /api/v2/pp_users endpoint to enforce authorization checks, ensuring only users with Administrator privileges can modify PP_SECURITY_PROFILE_ID. Validate the caller's permissions before processing any security profile changes.

Fix this in Project Contract Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64064 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64064 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data