CVE-2019-25684
Received Received - Intake
SQL Injection in OpenDocMan 1.3.4 Allows Data Extraction

Publication date: 2026-04-05

Last updated on: 2026-04-09

Assigner: VulnCheck

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-05
Last Modified
2026-04-09
Generated
2026-05-06
AI Q&A
2026-04-06
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
opendocman opendocman to 1.3.4 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

OpenDocMan 1.3.4 has an SQL injection vulnerability that allows attackers who are not authenticated to manipulate database queries. This is done by injecting malicious SQL code through the 'where' parameter in GET requests sent to the search.php page.

By exploiting this vulnerability, attackers can send specially crafted requests that alter the intended database queries, potentially extracting sensitive information from the database.


How can this vulnerability impact me? :

This vulnerability can have a significant impact as it allows unauthenticated attackers to extract sensitive information from the database. This could lead to data breaches, exposure of confidential information, and compromise of the integrity of the database.

The CVSS v3.1 score of 8.2 indicates a high severity, meaning the vulnerability is easy to exploit remotely without any privileges or user interaction, and it can result in high confidentiality impact and some integrity impact.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart