CVE-2025-2506
EDB pglogical Replication Connection Verification Bypass
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. To 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.
INFO
Published Date :
May 22, 2025, 4:15 p.m.
Last Modified :
May 23, 2025, 3:55 p.m.
Source :
20be33e2-bf35-4d13-8fad-18bd2f3e3659
Remotely Exploitable :
Yes !
Impact Score :
3.6
Exploitability Score :
1.6
Affected Products
The following products are affected by CVE-2025-2506
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2025-2506.
| URL | Resource |
|---|---|
| https://www.enterprisedb.com/docs/security/advisories/cve20252506/ |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2025-2506 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2025-2506 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
May. 22, 2025
Action Type Old Value New Value Added CVSS V3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N Added CWE CWE-862 -
New CVE Received by 20be33e2-bf35-4d13-8fad-18bd2f3e3659
May. 22, 2025
Action Type Old Value New Value Added 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. To 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. Added CVSS V3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N Added CWE CWE-862 Added Reference https://www.enterprisedb.com/docs/security/advisories/cve20252506/
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2025-2506 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2025-2506
weaknesses.