# CVE-2025-12807: FactoryTalk® DataMosaix™ Private Cloud SQL Injection

> Low-privilege users can execute sensitive database operations via exposed API endpoints in Rockwell FactoryTalk 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:** 9 Dec 2025
- **Updated:** 9 Dec 2025
- **Also known as:** GHSA-r8r9-2gq6-r5j8

## What is CVE-2025-12807?

CVE-2025-12807 is a high-severity SQL injection vulnerability in Rockwell Automation FactoryTalk® DataMosaix™ Private Cloud, published on 9 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security issue was discovered in DataMosaix Private Cloud, allowing users with low privilege to perform sensitive database operations through exposed API endpoints.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2025-12807?


## How do I fix CVE-2025-12807?

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

## Is CVE-2025-12807 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12807 and fix it if it is affected.

What it is: CVE-2025-12807 is a high-severity SQL injection vulnerability in Rockwell Automation FactoryTalk® DataMosaix™ Private Cloud, published on 9 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-12807 in the wild and no public exploit code.

Affected product: Rockwell Automation FactoryTalk® 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-2025-12807/ (Markdown: https://insights.sbomify.com/CVE-2025-12807/index.md)
```

## Sources

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

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