dbcve.org
PlacipyApplication · Prasklatechnology

CVE-2026-25806

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
PlaciPy is a placement management system designed for educational institutions. In version 1.0.0, the GET /api/students/:email PUT /api/students/:email/status, and DELETE /api/students/:email routes in backend/src/routes/student.routes.ts only enforce authentication using authenticateToken but do not enforce authorization. The application does not verify whether the authenticated user owns the student record being accessed, has an administrative / staff role, or is permitted to modify or delete the target student.

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

PlaciPy 1.0.0 contains an Insecure Direct Object Reference (IDOR) vulnerability where the GET /api/students/:email, PUT /api/students/:email/status, and DELETE /api/students/:email endpoints only enforce authentication via authenticateToken but lack authorization checks. Any authenticated user can access, modify, or delete any student record by specifying the target email, without verification of record ownership or admin/staff role privileges.

MitigationImplement role-based access control (RBAC) and ownership verification in the affected endpoints to ensure users can only access or modify their own student records unless they possess administrative or staff privileges.

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
PlacipyApplication
Affected:= 1.0.0

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
None
Integrity
High
Availability
None

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

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. Verify PlaciPy installation version
    Check the installed package version of Prasklatechnology Placipy using your package manager or dependency file (e.g., pip show placipy, requirements.txt, or package.json). Confirm the version is exactly 1.0.0.
    Affected if The installed version is 1.0.0, matching the affected version range.
  2. Confirm API endpoints are exposed
    Identify if the REST API is running and the student endpoints are accessible. Check your API router or route configuration files for the existence of /api/students/:email, /api/students/:email/status (PUT), and /api/students/:email (DELETE) routes.
    Affected if These three endpoints are defined and exposed in the application.
  3. Locate endpoint handler code for authorization logic
    Inspect the source code for the affected endpoints. Look for the route handlers for GET, PUT, and DELETE operations on /api/students/:email. Search for authorization or permission check functions within these handlers.
    Affected if The handlers contain authenticateToken calls but lack any subsequent role verification (e.g., check for admin/staff role) or ownership validation (e.g., verify the requesting user's email matches the :email parameter).
  4. Check for role-based access control implementation
    Search the codebase for RBAC mechanisms. Look for patterns like role_required, require_admin, check_role, or similar authorization decorators/functions. Verify whether these are applied to the student API endpoints.
    Affected if No RBAC decorators or authorization checks are present in the endpoint handlers, or they exist elsewhere but are not applied to these specific routes.
  5. Inspect authentication middleware usage
    Review the middleware or decorator chain applied to the student endpoints. Confirm that authenticateToken is the only access control applied, and that no follow-up authorization step verifies user identity against the requested resource.
    Affected if Only authentication is enforced (token validation passes) without subsequent authorization (user can only access their own record or requires admin privileges).

You are affected if running PlaciPy version 1.0.0 with the student API endpoints exposed and no authorization checks implemented beyond authentication token validation.

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) and ownership verification in the affected endpoints to ensure users can only access or modify their own student records unless they possess administrative or staff privileges.

Fix this in Placipy Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25806 — 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-2026-25806 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