{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-2506 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-2506 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-2506 is a medium-severity missing authorization vulnerability in EnterpriseDB BDR/PGD, published on 22 May 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-2506 and fix it if it is affected.\n\nWhat it is: CVE-2025-2506 is a medium-severity missing authorization vulnerability in EnterpriseDB BDR/PGD, published on 22 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-2506 in the wild and no public exploit code.\n\nAffected product: EnterpriseDB BDR/PGD. 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-2506/ (Markdown: https://insights.sbomify.com/CVE-2025-2506/index.md)","id":"CVE-2025-2506","markdown":"https://insights.sbomify.com/CVE-2025-2506/index.md","name":"CVE-2025-2506","record":{"aliases":[],"analysis":{"component_type":"database","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"PostgreSQL replication extension","requires_auth":"low_privilege","summary":"Users with CONNECT access can bypass replication checks to read replicated tables in pglogical and BDR/PGD environments.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EDB","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"When pglogical attempts to replicate data, it does not verify it is using a replication connection, which means a user with CONNECT access to a database configured for replication can execute the pglogical command to obtain read access to replicated tables. When pglogical runs it should verify it is running on a replication connection but does not perform this check. This vulnerability was introduced in the pglogical 3.x codebase, which is proprietary to EDB. The same code base has been integrated into BDR/PGD 4 and 5.\nTo exploit the vulnerability the attacker needs at least CONNECT permissions to a database configured for replication and must understand a number of pglogical3/BDR specific commands and be able to decode the binary protocol.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Missing authorization in BDR/PGD","id":"CVE-2025-2506","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in ChromeOS","id":"CVE-2025-2509"},"packages":[],"prev":{"headline":"Age Gate \u003c= 3.5.3 - Unauthenticated Local PHP File Inclusion via 'lang'","id":"CVE-2025-2505"},"products":["BDR/PGD","pglogical"],"published":"2025-05-22","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-08-26","vendors":["EnterpriseDB"]},"summary":"Users with CONNECT access can bypass replication checks to read replicated tables in pglogical and BDR/PGD environments.","url":"https://insights.sbomify.com/CVE-2025-2506/"}