CVE-2025-13780 Vulnerability Analysis & Exploit Details

CVE-2025-13780
Vulnerability Scoring

9.1

/10

Critical Risk

As a catastrophic security flaw, CVE-2025-13780 has severe implications, demanding immediate intervention.

Attack Complexity Details

Attack Complexity: Low
Exploits can be performed without significant complexity or special conditions.
Attack Vector: Network
Vulnerability is exploitable over a network without physical access.
Privileges Required: Low
Some privileges are necessary to exploit the vulnerability.
Scope: Changed
Successful exploitation can impact components beyond the vulnerable component.
User Interaction: None
No user interaction is necessary for exploitation.

CVE-2025-13780 Details

Status: Analyzed

Last updated: 🕢 19 Dec 2025, 19:51 UTC
Originally published on: 🕖 11 Dec 2025, 19:15 UTC

Time between publication and last update: 8 days

CVSS Release: version 3

CVSS3 Source

f86ef6dc-4d3a-42ad-8f28-e6d5547a5007

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L

CVE-2025-13780 Vulnerability Summary

CVE-2025-13780: pgAdmin versions up to 9.10 are affected by a Remote Code Execution (RCE) vulnerability that occurs when running in server mode and performing restores from PLAIN-format dump files. This issue allows attackers to inject and execute arbitrary commands on the server hosting pgAdmin, posing a critical risk to the integrity and security of the database management system and underlying data.

Assessing the Risk of CVE-2025-13780

Access Complexity Graph

The exploitability of CVE-2025-13780 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2025-13780

CVE-2025-13780 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2025-13780, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2025-13780, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

Confidentiality: High
Exploiting CVE-2025-13780 can result in unauthorized access to sensitive data, severely compromising data privacy.
Integrity: Low
Exploiting CVE-2025-13780 may cause minor changes to data without severely impacting its accuracy.
Availability: Low
CVE-2025-13780 may slightly degrade system performance without fully affecting service availability.

CVE-2025-13780 References

External References

https://github.com/pgadmin-org/pgadmin4/issues/9368

CWE Common Weakness Enumeration

CWE-94

CAPEC Common Attack Pattern Enumeration and Classification

Code Injection CAPEC-242 An adversary exploits a weakness in input validation on the target to inject new code into that which is currently executing. This differs from code inclusion in that code inclusion involves the addition or replacement of a reference to a code file, which is subsequently loaded by the target and used as part of the code of some application.
Leverage Executable Code in Non-Executable Files CAPEC-35 An attack of this type exploits a system's trust in configuration and resource files. When the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high.
Manipulating User-Controlled Variables CAPEC-77 This attack targets user controlled variables (DEBUG=1, PHP Globals, and So Forth). An adversary can override variables leveraging user-supplied, untrusted query variables directly used on the application server without any data sanitization. In extreme cases, the adversary can change variables controlling the business logic of the application. For instance, in languages like PHP, a number of poorly set default configurations may allow the user to override variables.

Vulnerable Configurations

cpe:2.3:a:pgadmin:pgadmin_4:-:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:-:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.0:-:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.0:-:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.0:rc1:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.0:rc1:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.0:beta1:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.0:beta1:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.0:beta2:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.0:beta2:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.0:beta3:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.0:beta3:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.0:beta4:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.0:beta4:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.1:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.1:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.2:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.2:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.3:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.3:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.4:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.4:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.5:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.5:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.6:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:1.6:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:2.0:-:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:2.0:-:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:2.0:rc1:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:2.0:rc1:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:2.0:rc2:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:2.0:rc2:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:2.1:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:2.1:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:3.0:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:3.0:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:3.1:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:3.1:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:3.2:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:3.2:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:3.3:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:3.3:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:3.4:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:3.4:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:3.5:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:3.5:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:3.6:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:3.6:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.0:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.0:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.1:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.1:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.2:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.2:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.3:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.3:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.4:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.4:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.5:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.5:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.6:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.6:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.7:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.7:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.8:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.8:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.9:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.9:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.10:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.10:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.11:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.11:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.12:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.12:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.13:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.13:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.14:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.14:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.15:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.15:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.16:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.16:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.17:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.17:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.18:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.18:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.19:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.19:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.20:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.20:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.21:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.21:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.22:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.22:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.23:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.23:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.24:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.24:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.25:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.25:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.26:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.26:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.27:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.27:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.28:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.28:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.29:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.29:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.30:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:4.30:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:5.0:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:5.0:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:5.1:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:5.1:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:5.2:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:5.2:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:5.3:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:5.3:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:5.4:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:5.4:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:5.5:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:5.5:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:5.6:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:5.6:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:5.7:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:5.7:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.0:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.0:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.1:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.1:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.2:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.2:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.3:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.3:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.4:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.4:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.5:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.5:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.6:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.6:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.7:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.7:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.8:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.8:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.9:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.9:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.10:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.10:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.11:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.11:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.12:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.12:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.13:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.13:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.14:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.14:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.15:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.15:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.16:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.16:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.17:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.17:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.18:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.18:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.19:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.19:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.20:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.20:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.21:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:6.21:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:7.0:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:7.0:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:7.1:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:7.1:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:7.2:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:7.2:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:7.3:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:7.3:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:7.4:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:7.4:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:7.5:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:7.5:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:7.6:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:7.6:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:7.7:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:7.7:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:7.8:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:7.8:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.0:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.0:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.1:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.1:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.2:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.2:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.3:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.3:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.4:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.4:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.5:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.5:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.6:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.6:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.7:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.7:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.8:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.8:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.9:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.9:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.10:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.10:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.11:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.11:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.12:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.12:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.13:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.13:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.14:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:8.14:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:9.0:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:9.0:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:9.1:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:9.1:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:9.2:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:9.2:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:9.3:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:9.3:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:9.4:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:9.4:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:9.5:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:9.5:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:9.6:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:9.6:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:9.7:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:9.7:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:9.8:*:*:*:*:postgresql:*:*
cpe:2.3:a:pgadmin:pgadmin_4:9.8:*:*:*:*:postgresql:*:*

Protect Your Infrastructure against CVE-2025-13780: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

CVE-2025-15166 – A vulnerability was found in itsourcecode Online Cake Ordering System 1.0. This affects an unknown function of the file /updatesupplier.php?action=...
CVE-2025-15165 – A vulnerability has been found in itsourcecode Online Cake Ordering System 1.0. The impacted element is an unknown function of the file /updatecust...
CVE-2025-15164 – A security flaw has been discovered in Tenda WH450 1.0.0.18. This affects an unknown part of the file /goform/SafeMacFilter. The manipulation of th...
CVE-2025-15163 – A vulnerability was identified in Tenda WH450 1.0.0.18. Affected by this issue is some unknown functionality of the file /goform/SafeEmailFilter. T...
CVE-2025-15067 – Unrestricted Upload of File with Dangerous Type vulnerability in Innorix Innorix WP allows Upload a Web Shell to a Web Server.This issue affects In...