Cyber Resilience

CVE-2019-25432

HighPublic PoC

Published: 20 February 2026

Published
20 February 2026
Modified
15 April 2026
KEV Added
Patch
CVSS Score v4 8.8 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0035 26.8th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2019-25432 is a high-severity SQL Injection (CWE-89) vulnerability. Its CVSS base score is 8.8 (High).

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

The strongest mitigations our analysis identified are NIST 800-53 SI-10 (Information Input Validation) and SI-2 (Flaw Remediation).

Deeper analysis

CVE-2019-25432 is an authentication bypass vulnerability in Part-DB version 0.4, stemming from SQL injection flaws in the login form's authentication parameters. Attackers can inject SQL syntax, such as a single quote followed by 'or', to bypass credential validation and gain unauthorized access to the application. The issue is classified under CWE-89 (Improper Neutralization of Special Elements used in an SQL Command) with a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), indicating high confidentiality impact from network-accessible exploitation without privileges or user interaction.

Unauthenticated remote attackers can exploit this vulnerability by submitting malicious input into the login form, allowing them to log in without valid credentials and access sensitive application data. The low attack complexity enables straightforward exploitation, potentially leading to full compromise of the Part-DB instance depending on user permissions and deployed features.

Advisories and proof-of-concept exploits are available from sources including the Part-DB GitHub repository (https://github.com/Part-DB/Part-DB/), Exploit-DB (https://www.exploit-db.com/exploits/47547), and VulnCheck (https://www.vulncheck.com/advisories/part-db-authentication-bypass-via-loginphp), which detail the vulnerability and potential remediation steps such as upgrading to a patched version or implementing input sanitization.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability details

Part-DB 0.4 contains an authentication bypass vulnerability that allows unauthenticated attackers to login by injecting SQL syntax into authentication parameters. Attackers can submit a single quote followed by 'or' in the login form to bypass credential validation and gain unauthorized…

more

access to the application.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

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.
Why these techniques?

Direct unauthenticated SQLi auth bypass in public web app login enables remote exploitation of the exposed application for initial access.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-24956Shared CWE-89
CVE-2026-33615Shared CWE-89
CVE-2025-28939Shared CWE-89
CVE-2021-47872Shared CWE-89
CVE-2025-28873Shared CWE-89
CVE-2019-25636Shared CWE-89
CVE-2026-32611Shared CWE-89
CVE-2026-42755Shared CWE-89
CVE-2024-53544Shared CWE-89
CVE-2026-21410Shared CWE-89

Affected Assets

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

prevent

SI-10 requires validation of information inputs to neutralize special elements used in SQL commands, directly preventing the SQL injection authentication bypass in CVE-2019-25432.

prevent

SI-2 mandates identification, reporting, and correction of system flaws, enabling patching of the SQL injection vulnerability in Part-DB's login form as recommended in advisories.

detect

RA-5 supports vulnerability scanning to identify SQL injection flaws like CVE-2019-25432 in authentication parameters prior to exploitation.

References