Cyber Resilience

CVE-2019-25684

HighPublic PoC

Published: 05 April 2026

Published
05 April 2026
Modified
09 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.0033 24.3th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2019-25684 is a high-severity SQL Injection (CWE-89) vulnerability in Opendocman Opendocman. 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 24.3th 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-25684 is an SQL injection vulnerability (CWE-89) affecting OpenDocMan version 1.3.4. The issue exists in the search.php component, where the 'where' parameter fails to properly sanitize user input, enabling attackers to inject arbitrary SQL code into database queries.

Unauthenticated remote attackers can exploit this vulnerability by sending GET requests to search.php with malicious SQL payloads in the 'where' parameter. Exploitation allows manipulation of database queries to extract sensitive information, with a CVSS v3.1 base score of 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N) reflecting high confidentiality impact, low integrity impact, and no availability impact.

Advisories and related resources include a VulnCheck advisory on the OpenDocMan SQL injection via the 'where' parameter, an Exploit-DB entry (46500) providing a proof-of-concept exploit, and the OpenDocMan project files on SourceForge.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability details

OpenDocMan 1.3.4 contains an SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries by injecting SQL code through the 'where' parameter. Attackers can send GET requests to search.php with malicious SQL payloads in the 'where' parameter to extract…

more

sensitive database information.

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.
T1213.006 Databases Collection
Adversaries may leverage databases to mine valuable information.
Why these techniques?

SQL injection in public-facing web app (search.php) directly enables remote exploitation (T1190) and extraction of sensitive data from the backend database (T1213.006).

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

CVEs Like This One

CVE-2018-25199Shared CWE-89
CVE-2026-27179Shared CWE-89
CVE-2025-0308Shared CWE-89
CVE-2019-25581Shared CWE-89
CVE-2026-27885Shared CWE-89
CVE-2019-25479Shared CWE-89
CVE-2026-1476Shared CWE-89
CVE-2019-25526Shared CWE-89
CVE-2025-69365Shared CWE-89
CVE-2019-25573Shared CWE-89

Affected Assets

opendocman
opendocman
≤ 1.3.4

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

prevent

SI-10 directly prevents SQL injection by requiring validation and sanitization of user inputs like the malicious 'where' parameter in search.php before database query execution.

prevent

SI-2 mandates timely identification, reporting, and correction of flaws such as the unsanitized 'where' parameter, eliminating the SQL injection vulnerability.

detect

RA-5 requires vulnerability scanning that identifies SQL injection issues like CVE-2019-25684 in search.php for prompt remediation.

References