# CVE-2017-5518: Server-side request forgery in n/a

> Remote attackers can exploit the media-file upload feature to perform Server-Side Request Forgery attacks, potentially accessing internal network resources.

- **Severity:** High 7.4 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A: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:** 17 Jan 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v2j5-972j-h7cp

## What is CVE-2017-5518?

CVE-2017-5518 is a high-severity server-side request forgery vulnerability in n/a, published on 17 Jan 2017. 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

The media-file upload feature in GeniXCMS through 0.0.8 allows remote attackers to conduct SSRF attacks via a URL, as demonstrated by a URL with an intranet IP address.

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

## Which versions are affected by CVE-2017-5518?

It affects 1 product.


Products: Metalgenix Genixcms.

## How do I fix CVE-2017-5518?

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

## Is CVE-2017-5518 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-3933](https://insights.sbomify.com/CVE-2015-3933/): MetalGenix GeniXCMS vulnerable to SQL Injection (critical 9.8)
- [CVE-2017-5959](https://insights.sbomify.com/CVE-2017-5959/): Cross-site request forgery in n/a (critical 9.8)
- [CVE-2017-5574](https://insights.sbomify.com/CVE-2017-5574/): SQL injection in n/a (critical 9.8)
- [CVE-2017-5575](https://insights.sbomify.com/CVE-2017-5575/): SQL injection in n/a (critical 9.8)
- [CVE-2017-5517](https://insights.sbomify.com/CVE-2017-5517/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5518 and fix it if it is affected.

What it is: CVE-2017-5518 is a high-severity server-side request forgery vulnerability in n/a, published on 17 Jan 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-5518 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-2017-5518/ (Markdown: https://insights.sbomify.com/CVE-2017-5518/index.md)
```

## Sources

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

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