CVE-2025-64062
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/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 attacker can assume the session and gain full access to the target user's data and privileges. Also, if the email parameter is left blank, the application defaults to the first user in the list, who is typically the application administrator, resulting in an immediate Privilege Escalation to the highest level.
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/V2/pp_users?email endpoint fails to validate that the email parameter matches the authenticated user's session. Attackers can manipulate the email parameter to access arbitrary user data, and submitting a blank email defaults to the first user in the list (typically the administrator), enabling immediate privilege escalation to the highest access level.
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.
-
Identify Primakon Project Contract Management versionLocate the application installation and check the version file, header, or about page for version 1.0.18. Common paths include the web root directory or administration panel.Affected if The installed version is exactly 1.0.18
-
Confirm the vulnerable API endpoint existsSend an HTTP GET request to /api/V2/pp_users (with no authentication or using any valid session) and verify the endpoint responds.Affected if The endpoint returns a response (success or error), indicating the vulnerable endpoint is exposed
-
Test email parameter authorization bypassSend a GET request to /api/V2/pp_users?email= (blank email parameter) and observe if user data is returned without proper authorization validation.Affected if The API returns user data (especially administrative account data) when a blank email is provided, indicating the default-to-first-user behavior is present
-
Verify arbitrary user data accessSend a GET request to /api/V2/pp_users?email=<any_valid_email> using a session that does not belong to that email address and check if data is returned.Affected if User data for other accounts is returned without proper session-to-email validation, confirming the authorization flaw
You are affected if Primakon Project Contract Management version 1.0.18 is installed AND the /api/V2/pp_users endpoint is accessible AND either blank email returns first-user data or arbitrary email addresses return unauthorized user information.
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 session validation ensuring the requested email matches the authenticated user's session, remove the default-to-first-user behavior, and enforce proper authorization checks before returning any user data.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64062 — 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-64062 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