# CVE-2020-37110: 60CycleCMS 2.5.2 - 'news.php' SQL Injection Vulnerability

> Attackers can inject SQL code via unvalidated input in news.php to extract or modify database contents in 60CycleCMS.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/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:** 3 Feb 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-jwv7-wwg8-6rjj

## What is CVE-2020-37110?

CVE-2020-37110 is a high-severity SQL injection vulnerability in Davidvg 60CycleCMS, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

60CycleCMS 2.5.2 contains an SQL injection vulnerability in news.php and common/lib.php that allows attackers to manipulate database queries through unvalidated user input. Attackers can exploit vulnerable query parameters like 'title' to inject malicious SQL code and potentially extract or modify database contents. This issue does not involve cross-site scripting.

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

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

It affects 1 product.


Products: Opensourcecms 60cyclecms.

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

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

## Is CVE-2020-37110 being exploited?

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

## Other vulnerabilities in Davidvg 60CycleCMS

- [CVE-2020-37111](https://insights.sbomify.com/CVE-2020-37111/): 60CycleCMS 2.5.2 - 'news.php' Cross-site Scripting (XSS) Vulnerability (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-37110 is a high-severity SQL injection vulnerability in Davidvg 60CycleCMS, published on 3 Feb 2026. 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-2020-37110 exists.

Affected product: Davidvg 60CycleCMS. 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-37110/ (Markdown: https://insights.sbomify.com/CVE-2020-37110/index.md)
```

## Sources

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

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