# CVE-2024-28735: Auth bypass in n/a

> An authenticated user can bypass authorization controls to modify any other user's password, leading to account takeover.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 20 Mar 2024
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-2647-rch5-5qg9

## What is CVE-2024-28735?

CVE-2024-28735 is a high-severity authentication bypass vulnerability in n/a, published on 20 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unit4 Financials by Coda versions prior to 2023Q4 suffer from an incorrect access control authorization bypass vulnerability which allows an authenticated user to modify the password of any user of the application via a crafted request.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2024-28735?

It affects 1 product.


Products: Unit4 Financials by Coda.

## How do I fix CVE-2024-28735?

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

## Is CVE-2024-28735 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-28735 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-28735 and fix it if it is affected.

What it is: CVE-2024-28735 is a high-severity authentication bypass vulnerability in n/a, published on 20 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-28735 exists.

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-2024-28735/ (Markdown: https://insights.sbomify.com/CVE-2024-28735/index.md)
```

## Sources

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

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