# CVE-2020-37111: 60CycleCMS 2.5.2 - 'news.php' Cross-site Scripting (XSS) Vulnerability

> Attackers can inject malicious scripts via GET parameters in news.php, allowing arbitrary script execution in victim browsers.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Feb 2026
- **Updated:** 24 May 2026
- **Also known as:** GHSA-jvr8-79f6-p83g

## What is CVE-2020-37111?

CVE-2020-37111 is a medium-severity cross-site scripting vulnerability in Davidvg 60CycleCMS, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

60CycleCMS 2.5.2 contains a cross-site scripting (XSS) vulnerability in news.php that allows attackers to inject malicious scripts through GET parameters. Attackers can craft malicious URLs with XSS payloads targeting the 'etsu' and 'ltsu' parameters to execute arbitrary scripts in victim's browsers. This issue does not involve SQL injection.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Opensourcecms 60cyclecms.

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

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

## Is CVE-2020-37111 being exploited?

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

## Other vulnerabilities in Davidvg 60CycleCMS

- [CVE-2020-37110](https://insights.sbomify.com/CVE-2020-37110/): 60CycleCMS 2.5.2 - 'news.php' SQL Injection Vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-37111 is a medium-severity cross-site scripting vulnerability in Davidvg 60CycleCMS, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37111 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-37111/ (Markdown: https://insights.sbomify.com/CVE-2020-37111/index.md)
```

## Sources

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

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