CVE-2026-25809
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 · uneditedPlaciPy is a placement management system designed for educational institutions. In version 1.0.0, the code evaluation endpoint does not validate the assessment lifecycle state before allowing execution. There is no check to ensure that the assessment has started, is not expired, or the submission window is currently open.
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 code evaluation endpoint in PlaciPy 1.0.0 lacks validation of the assessment lifecycle state before executing code, allowing unauthorized access regardless of whether an assessment has started, is within its submission window, or has expired. This is a logic/authorization bypass vulnerability in the assessment workflow.
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.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 installed PlaciPy versionCheck the installed version of PlaciPy in your environment using package manager commands or dependency inspection tools (e.g., pip show, package.json, requirements.txt)Affected if The installed version is PlaciPy 1.0.0 specifically
-
Locate the code evaluation endpointReview application routing, API definitions, or source code to identify the endpoint responsible for code evaluation/execution within the PlaciPy applicationAffected if A code evaluation endpoint exists and is accessible in the PlaciPy 1.0.0 deployment
-
Verify assessment lifecycle validation existsExamine the code evaluation endpoint implementation to determine if it performs checks for: (1) assessment has started, (2) current time is within the submission window, (3) assessment has not expired. Inspect the relevant source files or API handlers.Affected if The endpoint lacks one or more of the required lifecycle state validations (assessment started, submission window open, not expired)
-
Test endpoint behavior with expired or not-yet-started assessmentIf possible, attempt to access the code evaluation endpoint using an assessment that has either not started or has already expired. Observe whether the endpoint allows code execution despite the assessment lifecycle state.Affected if The endpoint accepts and executes code without verifying the assessment lifecycle state
You are affected if you have PlaciPy version 1.0.0 deployed and its code evaluation endpoint permits execution without validating whether the assessment has started, is within its submission window, or has not expired.
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 validation checks on the code evaluation endpoint to verify the assessment has started, the submission window is currently open, and the assessment has not expired before allowing execution.
- 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-2026-25809 — 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-2026-25809 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