# CVE-2020-28927: Cross-site scripting in n/a

> Stored XSS in Magicpin allows attackers to steal admin cookies when the admin views the user management section.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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:** 23 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6542-cc58-3fvq

## What is CVE-2020-28927?

CVE-2020-28927 is a medium-severity cross-site scripting vulnerability in n/a, published on 23 Nov 2020. 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

There is a Stored XSS in Magicpin v2.1 in the User Registration section. Each time an admin visits the manage user section from the admin panel, the XSS triggers and the attacker can able to steal the cookie according to the crafted payload.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2020-28927?

It affects 1 product.


Products: Magicpin Magicpin.

## How do I fix CVE-2020-28927?

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

## Is CVE-2020-28927 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-31447](https://insights.sbomify.com/CVE-2022-31447/): XML external entity in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-28927 and fix it if it is affected.

What it is: CVE-2020-28927 is a medium-severity cross-site scripting vulnerability in n/a, published on 23 Nov 2020. 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-2020-28927 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-2020-28927/ (Markdown: https://insights.sbomify.com/CVE-2020-28927/index.md)
```

## Sources

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

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