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

> Attackers can use low-privilege CSRF tokens to perform actions as high-privileged users in PONTON X/P Messenger.

- **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:** 13 Mar 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xgh6-mwxq-8jp5

## What is CVE-2021-45886?

CVE-2021-45886 is a high-severity vulnerability in n/a, published on 13 Mar 2022. 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

An issue was discovered in PONTON X/P Messenger before 3.11.2. Anti-CSRF tokens are globally valid, making the web application vulnerable to a weakened version of CSRF, where an arbitrary token of a low-privileged user (such as operator) can be used to confirm actions of higher-privileged ones (such as xpadmin).

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

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

It affects 1 product.


Products: Ponton X\/P Messenger.

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

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

## Is CVE-2021-45886 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-45887](https://insights.sbomify.com/CVE-2021-45887/): Path traversal in n/a (critical 9.8)
- [CVE-2021-45889](https://insights.sbomify.com/CVE-2021-45889/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2021-45888](https://insights.sbomify.com/CVE-2021-45888/): Cross-site scripting in n/a (medium 4.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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