# CVE-2018-19601: Server-side request forgery in n/a

> Attackers can exploit an SSRF vulnerability in Rhymix CMS via SVG upload to access internal resources or bypass security controls.

- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jan 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-756g-77hp-9phc

## What is CVE-2018-19601?

CVE-2018-19601 is a critical server-side request forgery vulnerability in n/a, published on 3 Jan 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Rhymix CMS 1.9.8.1 allows SSRF via an index.php?module=admin&act=dispModuleAdminFileBox SVG upload.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2018-19601?

It affects 1 product.


Products: Rhymix Rhymix.

## How do I fix CVE-2018-19601?

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

## Is CVE-2018-19601 being exploited?

There is no known exploitation of CVE-2018-19601 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2025-45242](https://insights.sbomify.com/CVE-2025-45242/): Path traversal in n/a (high 7.7)
- [CVE-2018-19600](https://insights.sbomify.com/CVE-2018-19600/): Cross-site scripting in n/a (medium 4.8)
- [CVE-2024-55089](https://insights.sbomify.com/CVE-2024-55089/): XML external entity in Rhymix (medium 4.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-19601 and fix it if it is affected.

What it is: CVE-2018-19601 is a critical server-side request forgery vulnerability in n/a, published on 3 Jan 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-19601 in the wild and no public exploit code.

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

## Sources

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

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