# CVE-2020-18416: Cross-site request forgery in n/a

> Attackers can exploit CSRF to modify payment information and execute arbitrary code in Jymusic, requiring user interaction.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **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-23qq-wph5-jwww

## What is CVE-2020-18416?

CVE-2020-18416 is a medium-severity 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

An cross site request forgery (CSRF) vulnerability discovered in Jymusic v2.0.0.,that allows attackers to execute arbitrary code via /admin.php?s=/addons/config.html&id=6 to modify payment information.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Jyuu Jymusic.

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

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

## Is CVE-2020-18416 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-18416 is a medium-severity 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-18416 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-18416/ (Markdown: https://insights.sbomify.com/CVE-2020-18416/index.md)
```

## Sources

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

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