Cyber Resilience

CVE-2025-12764

Pgadmin 4 ≤ 9.10

Published
13 November 2025
Modified
19 November 2025
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0039 32th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2025-12764 is a high-severity LDAP Injection (CWE-90) vulnerability in Pgadmin Pgadmin 4. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 32th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

pgAdmin <= 9.9 is affected by an LDAP injection vulnerability in the LDAP authentication flow that allows an attacker to inject special LDAP characters in the username, causing the DC/LDAP server and the client to process an unusual amount of…

more

data DOS.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-17346Same product: Pgadmin Pgadmin 4
CVE-2026-12050Same product: Pgadmin Pgadmin 4
CVE-2026-7815Same product: Pgadmin Pgadmin 4
CVE-2023-0241Same product: Pgadmin Pgadmin 4
CVE-2026-7818Same product: Pgadmin Pgadmin 4
CVE-2026-12044Same product: Pgadmin Pgadmin 4
CVE-2026-12046Same product: Pgadmin Pgadmin 4
CVE-2026-7816Same product: Pgadmin Pgadmin 4
CVE-2026-17347Same product: Pgadmin Pgadmin 4
CVE-2026-7814Same product: Pgadmin Pgadmin 4

Affected Assets

pgadmin
pgadmin 4
≤ 9.10

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.2.6

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover LDAP injection flaws through static analysis or crafted test cases.

Input validation directly stops untrusted data from reaching an LDAP query builder without neutralization of special characters.

Secure engineering principles require safe query construction and escaping that structurally prevents LDAP injection.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input neutralization and query parameterization to prevent LDAP injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development catches LDAP injection via dynamic analysis or fuzzing, but does not prevent it at the source.

prevents

Secure development lifecycle mandates input validation and query construction practices that directly prevent LDAP injection.

prevents

Application security requirements include explicit rules for safe construction of directory queries, mitigating LDAP injection.

prevents

Secure coding standards require proper neutralization of LDAP special characters, directly eliminating this weakness.

mitigates

Secure architecture principles encourage safe query interfaces but do not prescribe the specific coding controls needed for LDAP injection.

none

Information access restriction limits who can query LDAP but does not address how queries are built.

References