# CVE-2025-5690: Cursor allows PostgreSQL Anonymizer masked user to gain unauthorized access to authentic data

> A masked user can bypass masking rules to read original data when dynamic masking is enabled in PostgreSQL Anonymizer.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 4 Jun 2025
- **Updated:** 5 Jun 2025
- **Also known as:** GHSA-f87m-rhgw-vj35

## What is CVE-2025-5690?

CVE-2025-5690 is a medium-severity vulnerability in DALIBO PostgreSQL Anonymizer, published on 4 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PostgreSQL Anonymizer v2.0 and v2.1 contain a vulnerability that allows a masked user to bypass the masking rules defined on a table and read the original data using a database cursor or the --insert option of pg_dump. This problem occurs only when dynamic masking is enabled, which is not the default setting. The problem is resolved in version 2.2.1

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2025-5690 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5690 is a medium-severity vulnerability in DALIBO PostgreSQL Anonymizer, published on 4 Jun 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-2025-5690 exists.

Affected product: DALIBO PostgreSQL Anonymizer. 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-5690/ (Markdown: https://insights.sbomify.com/CVE-2025-5690/index.md)
```

## Sources

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

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