CVE-2019-25684 Details
Description
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 sensitive database information.
A SQL injection vulnerability has been identified in OpenDocMan version 1.3.4. This vulnerability allows unauthenticated attackers to manipulate database queries by injecting SQL code through the 'where' parameter. Attackers can exploit this issue by sending GET requests to search.php with malicious SQL payloads, potentially leading to the extraction of sensitive database information.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Apr 6, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://sourceforge.net/projects/opendocman/files/ | [email protected] | Product |
| https://www.exploit-db.com/exploits/46500 | [email protected] | ExploitVDB Entry |
| https://www.vulncheck.com/advisories/opendocman-sql-injection-via-where-parameter | [email protected] | Third Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-89 | Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| opendocman opendocman | <= 1.3.4 |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 6, 2026 | CVE Translated | [email protected] |
| Jul 24, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Apr 9, 2026 | Initial Analysis | [email protected] |
| Apr 5, 2026 | New CVE Received | [email protected] |