# CVE-2018-14711: Cross-site request forgery in n/a

> Attackers can perform state-changing actions on ASUS RT-AC3200 routers via crafted URLs due to missing CSRF protection.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/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:** 13 May 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mmf2-45w8-23q8

## What is CVE-2018-14711?

CVE-2018-14711 is a medium-severity vulnerability in n/a, published on 13 May 2019. 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

Missing cross-site request forgery protection in appGet.cgi on ASUS RT-AC3200 version 3.0.0.4.382.50010 allows attackers to cause state-changing actions with specially crafted URLs.

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

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

It affects 1 product.


Products: Asus Rt-Ac3200 Firmware.

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

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

## Is CVE-2018-14711 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-14714](https://insights.sbomify.com/CVE-2018-14714/): Command injection in n/a (critical 9.8)
- [CVE-2018-14713](https://insights.sbomify.com/CVE-2018-14713/): Information disclosure in n/a (high 8.1)
- [CVE-2018-14712](https://insights.sbomify.com/CVE-2018-14712/): Command injection in n/a (medium 6.5)
- [CVE-2018-14710](https://insights.sbomify.com/CVE-2018-14710/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-14711 is a medium-severity vulnerability in n/a, published on 13 May 2019. 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-2018-14711 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-14711/ (Markdown: https://insights.sbomify.com/CVE-2018-14711/index.md)
```

## Sources

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

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