# CVE-2026-81674: Multiple Vulnerabilities in TOOOLS' iSquad

> Attackers can inject SQL into the getVideoNextPrev endpoint to read database data and expose internal query structures in TOOOLS' iSquad.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-5w9h-62pq-pj3g

## What is CVE-2026-81674?

CVE-2026-81674 is a critical SQL injection vulnerability in TOOOLS iSquad, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The endpoint ‘/ws/apiprensa/getVideoNextPrev’ is vulnerable to SQL injection via the id_ambito parameter. Unsanitized input is directly incorporated into a MariaDB query, allowing attackers to inject SQL syntax that interrupts the query's execution. The vulnerability results in detailed database error messages and exposes the internal structure of the queries, which could facilitate further exploitation.

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

## Which versions are affected by CVE-2026-81674?


## How do I fix CVE-2026-81674?

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

## Is CVE-2026-81674 being exploited?

There is no known exploitation of CVE-2026-81674 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-81674 and fix it if it is affected.

What it is: CVE-2026-81674 is a critical SQL injection vulnerability in TOOOLS iSquad, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-81674 in the wild and no public exploit code.

Affected product: TOOOLS iSquad. 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-2026-81674/ (Markdown: https://insights.sbomify.com/CVE-2026-81674/index.md)
```

## Sources

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

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