# CVE-2024-7953: DataEdgePlatform DataMosaix™ Private Cloud

> An attacker can escalate privileges to become a project administrator, allowing them to create, modify, and delete their own projects in DataMosaix Private Cloud.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA: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:** 1 Sep 2026
- **Updated:** 1 Sep 2026
- **Also known as:** GHSA-gc56-ff3g-9v5x

## What is CVE-2024-7953?

CVE-2024-7953 is a high-severity vulnerability in Rockwell Automation DataEdgePlatform DataMosaix™ Private Cloud, published on 1 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability exists in the affected products that allows a threat actor to create a project and become the administrator for it. If exploited, a threat actor could create, modify, and delete their own project.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2024-7953 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-7953 is a high-severity vulnerability in Rockwell Automation DataEdgePlatform DataMosaix™ Private Cloud, published on 1 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-7953 in the wild and no public exploit code.

Affected product: Rockwell Automation DataEdgePlatform DataMosaix™ Private Cloud. 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-7953/ (Markdown: https://insights.sbomify.com/CVE-2024-7953/index.md)
```

## Sources

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

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