# CVE-2025-3113: Improper Access Control in Delphix Masking Engine

> Authenticated users can access internal database schemas and export sensitive configuration data via the Connector functionality.

- **Severity:** Critical 9.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **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:** 17 Apr 2025
- **Updated:** 17 Apr 2025
- **Also known as:** GHSA-j2wh-x4mx-4v64

## What is CVE-2025-3113?

CVE-2025-3113 is a critical missing authorization vulnerability in Perforce Delphix, published on 17 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A valid, authenticated user with sufficient privileges and who is aware of Continuous Compliance’s internal database configurations can leverage the application’s built-in Connector functionality to access Continuous Compliance’s internal database. This allows the user to explore the internal database schema and export its data, including the properties of Connecters and Rule Sets.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2025-3113 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3113 is a critical missing authorization vulnerability in Perforce Delphix, published on 17 Apr 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-3113 in the wild and no public exploit code.

Affected product: Perforce Delphix. 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-3113/ (Markdown: https://insights.sbomify.com/CVE-2025-3113/index.md)
```

## Sources

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

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