# CVE-2020-29574: CyberoamOS (CROS) SQL Injection

> Unauthenticated attackers can execute arbitrary SQL statements via the WebAdmin interface of Cyberoam OS, potentially compromising database integrity and confidentiality.

- **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:** Yes, since 6 Feb 2025 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Dec 2020
- **Updated:** 15 Aug 2026
- **Also known as:** GHSA-v2fr-wv49-j53x

## What is CVE-2020-29574?

CVE-2020-29574 is a critical SQL injection vulnerability in n/a, published on 11 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An SQL injection vulnerability in the WebAdmin of Cyberoam OS through 2020-12-04 allows unauthenticated attackers to execute arbitrary SQL statements remotely.

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

## Which versions are affected by CVE-2020-29574?

It affects 1 product.


Products: Sophos Cyberoamos.

## How do I fix CVE-2020-29574?

No fix has been published for CVE-2020-29574 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 27 Feb 2025.

## Is CVE-2020-29574 being exploited?

Yes. Attackers have exploited CVE-2020-29574 in the wild since at least 6 Feb 2025, including in ransomware campaigns.

## Other vulnerabilities in n/a

- [CVE-2019-17059](https://insights.sbomify.com/CVE-2019-17059/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-29574 and fix it if it is affected.

What it is: CVE-2020-29574 is a critical SQL injection vulnerability in n/a, published on 11 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2020-29574 in the wild since at least 6 Feb 2025, including in ransomware campaigns.

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-2020-29574/ (Markdown: https://insights.sbomify.com/CVE-2020-29574/index.md)
```

## Sources

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

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