# CVE-2020-28403: Cross-site request forgery in n/a

> An attacker can exploit CSRF to modify user privileges, potentially granting themselves administrative access or removing existing admin accounts.

- **Severity:** High 8.0 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:L/S:U/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Jan 2021
- **Updated:** 30 May 2025
- **Also known as:** GHSA-4mmf-jfc6-j4wj

## What is CVE-2020-28403?

CVE-2020-28403 is a high-severity vulnerability in n/a, published on 29 Jan 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A Cross-Site Request Forgery (CSRF) vulnerability exists in Star Practice Management Web version 2019.2.0.6, allowing an attacker to change the privileges of any user of the application. This can be used to grant himself administrative role or remove the administrative account of the application.

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

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

It affects 1 product.


Products: Iris Star.

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

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

## Is CVE-2020-28403 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-28403 is a high-severity vulnerability in n/a, published on 29 Jan 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-28403 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-28403/ (Markdown: https://insights.sbomify.com/CVE-2020-28403/index.md)
```

## Sources

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

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