CVE-2026-25876 is a broken object level authorization flaw in PlaciPy 1.0.0, rated 9.1. The results routes confirm a user is logged in but not that the data is theirs, so one request can return all results for an assessment. The record names no fixed version.
What's affected
- Product: PlaciPy, a placement management system for educational institutions.
- Affected: version 1.0.0.
- Fixed version: none is stated in the record. Check the GitHub advisory and the project's repository for a patched release.
- Weakness: the results routes check authentication but not ownership.
How to check if you're exposed
PlaciPy is deployed from source, so look at the version in your checkout and at how your deployment is exposed:
git -C /path/to/assessment-placipy describe --tags
grep '"version"' /path/to/assessment-placipy/package.json
If you run 1.0.0, treat the instance as affected. Also check whether it is reachable from the internet and what student data it holds.
What to do now
- Read the GitHub advisory and apply the fix or patch it describes, if one has been published.
- Do not expose the application to the internet until you have confirmed a fix, or put it behind a VPN or an authenticating proxy.
- Limit result access to staff roles at the proxy layer if you can, until a fix is confirmed.
- Log every result query with the caller and the target identifier.
- Review access logs for requests you cannot explain, and tell the people responsible for student data if you find any.
- Plan for fixes in all the related PlaciPy advisories, since several were reported together.
Why it matters
The record lists CWE-862, missing authorization. Result data is among the most sensitive in a placement system: scores and rankings tied to named students. When the route trusts a user supplied identifier, a signed in student can read everyone else's.
The project is small and the record gives no fixed version, so the practical step is to reduce exposure while you wait. Placement systems hold personal data about students, which raises the stakes of any access control gap. The record does not mark this CVE as exploited in the wild.
Quick check
Is a login screen enough to protect results?
No. The server must check that the logged in user is allowed to see the specific records requested.
Sources
Last reviewed: 19 October 2026.
