# CVE-2021-31152: Cross-site request forgery in n/a

> An attacker can exploit CSRF to enable remote access and change passwords on Multilaser AC1200 routers, leading to unauthorized control.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 14 Apr 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-75mj-58g7-9g7g

## What is CVE-2021-31152?

CVE-2021-31152 is a high-severity vulnerability in n/a, published on 14 Apr 2021. 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

Multilaser Router AC1200 V02.03.01.45_pt contains a cross-site request forgery (CSRF) vulnerability. An attacker can enable remote access, change passwords, and perform other actions through misconfigured requests, entries, and headers.

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

## Which versions are affected by CVE-2021-31152?

It affects 1 product.


Products: Multilaser Ac1200 Re018 Firmware.

## How do I fix CVE-2021-31152?

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

## Is CVE-2021-31152 being exploited?

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

Public exploit code:

- Multilaser Router RE018 AC1200 - Cross-Site Request Forgery (Enable Remote Access) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-31152 and fix it if it is affected.

What it is: CVE-2021-31152 is a high-severity vulnerability in n/a, published on 14 Apr 2021. 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-2021-31152 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-2021-31152/ (Markdown: https://insights.sbomify.com/CVE-2021-31152/index.md)
```

## Sources

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

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