CVE-2025-64065
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 · uneditedThe 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-privileged user to execute a direct PATCH request, enabling them to impersonate any other arbitrary user, including application Administrators. This is due to a Broken Function Level Authorization failure (the function doesn't check the caller's privilege) compounded by an Insecure Design that permits a session switch without requiring the target user's password or an administrative token and only needs email of user.
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 confidenceThe Primakon Pi Portal 1.0.18 API endpoint /api/V2/pp_udfv_admin lacks proper authorization checks on the LoginAs/impersonation feature. Any authenticated low-privileged user can send a direct PATCH request with a target user's email to impersonate that user, including administrators, due to a Broken Function Level Authorization failure combined with Insecure Design that requires no password or admin token.
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= 1.0.18CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Primakon Project Contract Management versionCheck installed version of Primakon Project Contract Management - review application about page, software inventory, or contact system administrator for version confirmationAffected if Version is 1.0.18 exactly (this is the only affected version per vendor disclosure)
-
Confirm API endpoint existsLocate server logs, API documentation, or web application firewall rules that reference the /api/V2/pp_udfv_admin endpoint; use HTTP fingerprinting if permitted to probe for endpoint existenceAffected if The /api/V2/pp_udfv_admin endpoint is present and responds to requests in the environment
-
Check user privilege model for impersonation featureReview application role definitions and permission matrices; identify if the LoginAs or impersonation functionality in pp_udfv_admin is accessible to non-administrator authenticated usersAffected if Low-privileged (non-admin) authenticated users have access to impersonation/LoginAs functionality
-
Test authorization enforcement on PATCH requestsAs a low-privileged authenticated user, attempt a PATCH request to /api/V2/pp_udfv_admin with a target user's email to trigger impersonation; verify if the request succeeds without requiring admin token or target passwordAffected if The PATCH request succeeds and allows impersonation without proper admin authorization checks
Environment is affected if Primakon Project Contract Management version 1.0.18 is running AND the /api/V2/pp_udfv_admin endpoint exists AND low-privileged users can successfully impersonate other users including administrators via unauthenticated PATCH requests.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement server-side authorization checks to verify the requesting user has administrative privileges before allowing impersonation, and require either an admin token or the target user's password for session switching.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64065 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-64065 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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