{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5690 exists.","fix":"No fix has been published for CVE-2025-5690 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-5690 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5690 exists.\n\nAffected product: DALIBO PostgreSQL Anonymizer. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-5690/ (Markdown: https://insights.sbomify.com/CVE-2025-5690/index.md)","id":"CVE-2025-5690","markdown":"https://insights.sbomify.com/CVE-2025-5690/index.md","name":"CVE-2025-5690","record":{"aliases":["GHSA-f87m-rhgw-vj35"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"PostgreSQL Anonymizer","requires_auth":"low_privilege","summary":"A masked user can bypass masking rules to read original data when dynamic masking is enabled in PostgreSQL Anonymizer.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"PostgreSQL","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"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","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Cursor allows PostgreSQL Anonymizer masked user to gain unauthorized access to authentic data","id":"CVE-2025-5690","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Lead Form Data Collection to CRM \u003c= 3.1 - Missing Authorization to Authenticated (Subscriber+) Many Actions","id":"CVE-2025-5692"},"packages":[],"prev":{"headline":"Improper Permission Management in SSH Session Handling","id":"CVE-2025-5689"},"products":["PostgreSQL Anonymizer"],"published":"2025-06-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-05","vendors":["DALIBO"]},"summary":"A masked user can bypass masking rules to read original data when dynamic masking is enabled in PostgreSQL Anonymizer.","url":"https://insights.sbomify.com/CVE-2025-5690/"}