CVE-2026-25814
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, User-controlled query parameters are passed directly into DynamoDB query/filter construction without validation or sanitization.
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 confidencePlaciPy 1.0.0 contains a NoSQL injection vulnerability where user-controlled query parameters are passed directly into DynamoDB query/filter construction without validation or sanitization. Attackers can manipulate query parameters to access, modify, or delete unauthorized data in the DynamoDB backend.
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 PlaciPy installationRun 'pip show placipy' or check your Python environment's installed packages for 'placipy' or 'PlaciPy'Affected if PlaciPy version 1.0.0 is installed
-
Verify DynamoDB integration is in useSearch project code for imports or usage of boto3 DynamoDB client, DynamoDB resource, or dynamodb table operationsAffected if Code uses boto3.resource('dynamodb') or boto3.client('dynamodb') to interact with DynamoDB
-
Locate query parameter handling codeSearch for functions that handle user input and construct DynamoDB queries, filter expressions, or KeyConditionExpressions; look for patterns like Table.query(), Table.scan(), or raw boto3 DynamoDB API calls accepting user-controlled parametersAffected if User-supplied parameters are passed to DynamoDB query methods like filter_expression, KeyConditionExpression, or ExpressionAttributeValues
-
Inspect input validation on query parametersReview the code paths where user input flows into DynamoDB queries; check if there is allowlist validation, type checking, or parameterized query construction before the query is executedAffected if User-controlled parameters are used directly in DynamoDB query construction without validation, sanitization, or parameterized binding
A user is affected if they have PlaciPy 1.0.0 installed AND their application passes unsanitized user input into DynamoDB query or filter expressions.
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 strict input validation and parameterized query construction for all user-supplied parameters before using them in DynamoDB queries. Use allowlist validation for expected parameter types and formats.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25814 — 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-25814 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