Safeguard
Vulnerability Analysis•

CVE-2026-25814: DynamoDB Query Injection in PlaciPy 1.0.0

CVE-2026-25814 passes user query parameters into PlaciPy DynamoDB queries without validation (CVSS 9.8). Restrict exposure and read the advisory.

Safeguard Security Team
3 min read

CVE-2026-25814 is an injection flaw in PlaciPy 1.0.0, scored 9.8. User controlled query parameters go directly into DynamoDB query and filter construction with no validation or sanitising. The record names no fixed version, so check the advisory before relying on any release.

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: query parameters are passed unvalidated into DynamoDB queries and filters.

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

  1. Read the GitHub advisory and apply the fix or patch it describes, if one has been published.
  2. Do not expose the application to the internet until you have confirmed a fix, or put it behind a VPN or an authenticating proxy.
  3. Restrict the IAM role used by the application to the tables and actions it needs.
  4. Validate parameters against an allow list before building any query, if you maintain a fork.
  5. Review access logs for requests you cannot explain, and tell the people responsible for student data if you find any.
  6. Plan for fixes in all the related PlaciPy advisories, since several were reported together.

Why it matters

The record lists CWE-74, improper neutralisation of special elements in output. NoSQL stores avoid SQL syntax but are not immune to injection. If a caller can shape the filter expression or key condition, they can read items the code never meant to return.

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

Does NoSQL mean no injection?

No. Any time user input shapes a query structure or expression, injection is possible.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.