# CVE-2020-18414: Cross-site scripting in n/a

> Attackers can execute arbitrary code via stored XSS in Chaoji CMS admin settings, potentially compromising user sessions and site integrity.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Jun 2023
- **Updated:** 4 Dec 2024
- **Also known as:** GHSA-g2c3-62p7-49qv

## What is CVE-2020-18414?

CVE-2020-18414 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 Jun 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Stored cross site scripting (XSS) vulnerability in Chaoji CMS v2.18 that allows attackers to execute arbitrary code via /index.php?admin-master-webset.

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

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

It affects 1 product.


Products: Chaoji Cms Project Chaoji Cms.

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

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

## Is CVE-2020-18414 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-19962](https://insights.sbomify.com/CVE-2020-19962/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2020-18410](https://insights.sbomify.com/CVE-2020-18410/): Cross-site scripting in n/a (medium 4.8)
- [CVE-2020-18413](https://insights.sbomify.com/CVE-2020-18413/): Cross-site scripting in n/a (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-18414 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 Jun 2023. An attacker needs administrator access to exploit it, 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-18414 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-2020-18414/ (Markdown: https://insights.sbomify.com/CVE-2020-18414/index.md)
```

## Sources

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

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