# CVE-2021-3262: SQL injection in n/a

> Attackers can inject SQL commands into search queries to read or modify student busing data in TripSpark VEO and NovusEDU.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Aug 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-9hqp-4cqc-x83x

## What is CVE-2021-3262?

CVE-2021-3262 is a critical SQL injection vulnerability in n/a, published on 29 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TripSpark VEO Transportation-2.2.x-XP_BB-20201123-184084 NovusEDU-2.2.x-XP_BB-20201123-184084 allows unsafe data inputs in POST body parameters from end users without sanitizing using server-side logic. It was possible to inject custom SQL commands into the "Student Busing Information" search queries.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2021-3262?

It affects 2 products.


Products: Trispark Novusedu, Trispark Veo Transportation.

## How do I fix CVE-2021-3262?

No fix has been published for CVE-2021-3262 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-3262 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-3262 exists.

Public exploit code:

- CVE-2021-3262 - Blind SQL Injection in the editOEN parameter of TripSpark VEO Transportation / NovusEDU. Unauthenticated, internet-facing. Payloads, annotated requests, and evidence. (github_poc): https://github.com/l0lsec/CVE-2021-3262

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-3262 and fix it if it is affected.

What it is: CVE-2021-3262 is a critical SQL injection vulnerability in n/a, published on 29 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-3262 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-3262/ (Markdown: https://insights.sbomify.com/CVE-2021-3262/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-3262
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-3262
- OSV: https://osv.dev/vulnerability/CVE-2021-3262

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-3262/
Summaries are generated and may contain mistakes; the official description above is the record.