# CVE-2023-28876: Missing authorization in n/a

> Attackers can delete comments on files uploaded by other users due to broken access control in Filerun.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-7j5j-2vx3-v5r2

## What is CVE-2023-28876?

CVE-2023-28876 is a medium-severity missing authorization vulnerability in n/a, published on 6 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A Broken Access Control issue in comments to uploaded files in Filerun through Update 20220202 allows attackers to delete comments on files uploaded by other users.

## Which versions are affected by CVE-2023-28876?

It affects 1 product.


Products: Afian Filerun.

## How do I fix CVE-2023-28876?

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

## Is CVE-2023-28876 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-30470](https://insights.sbomify.com/CVE-2022-30470/): Code injection in n/a (critical 9.8)
- [CVE-2022-30469](https://insights.sbomify.com/CVE-2022-30469/): SQL injection in n/a (high 8.8)
- [CVE-2021-35504](https://insights.sbomify.com/CVE-2021-35504/): Command injection in n/a (high 7.2)
- [CVE-2021-35505](https://insights.sbomify.com/CVE-2021-35505/): Command injection in n/a (high 7.2)
- [CVE-2018-7734](https://insights.sbomify.com/CVE-2018-7734/): SQL injection in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-28876 and fix it if it is affected.

What it is: CVE-2023-28876 is a medium-severity missing authorization vulnerability in n/a, published on 6 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-28876 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-2023-28876/ (Markdown: https://insights.sbomify.com/CVE-2023-28876/index.md)
```

## Sources

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

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