# CVE-2024-2292: Access Control Vulnerabilities lead to Violation of Privacy and Modification of Personal Data

> Unauthorized users can view and modify other users' personal data due to missing access controls in ChangeWeb UnifiedTransform.

- **Severity:** High 7.1 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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:** 20 Mar 2025
- **Updated:** 15 Oct 2025
- **Also known as:** GHSA-xv4c-2443-pc28

## What is CVE-2024-2292?

CVE-2024-2292 is a high-severity missing authorization vulnerability in changeweb/unifiedtransform, published on 20 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Due to a lack of access control, unauthorized users are able to view and modify information pertaining to other users.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2024-2292 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-2292 is a high-severity missing authorization vulnerability in changeweb/unifiedtransform, published on 20 Mar 2025. 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-2292 exists.

Affected product: changeweb/unifiedtransform. 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-2292/ (Markdown: https://insights.sbomify.com/CVE-2024-2292/index.md)
```

## Sources

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

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