CVE-2019-25580
SQL Injection in ownDMS 4.7 Allows Database Data Exposure
Publication date: 2026-03-21
Last updated on: 2026-04-15
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| owndms | owndms | to 4.7 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-434 | The product allows the upload or transfer of dangerous file types that are automatically processed within its environment. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2019-25580 is a high-severity SQL injection vulnerability in ownDMS version 4.7. It allows unauthenticated attackers to inject malicious SQL code through the IMG parameter in certain PHP scripts such as pdfstream.php, imagestream.php, and anyfilestream.php. By sending specially crafted GET requests, attackers can execute arbitrary SQL queries on the database.
This injection can be used to extract sensitive information from the database, including database version and database names, without requiring any privileges or user interaction.
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized access to sensitive database information. Attackers can retrieve critical data such as database version and names, which can be leveraged for further attacks or data breaches.
Since the vulnerability does not require authentication or user interaction, it can be exploited remotely and easily, increasing the risk of data exposure.
The CVSS v4 score of 8.8 reflects the high severity and potential impact of this vulnerability.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': "This SQL injection vulnerability can be detected by sending crafted HTTP GET requests to the vulnerable endpoints (pdfstream.php, imagestream.php, anyfilestream.php) with malicious SQL payloads in the IMG parameter and observing the server's response for signs of SQL injection."}, {'type': 'paragraph', 'content': 'For example, you can use curl commands to test the vulnerability by injecting UNION SELECT statements or other SQL payloads to see if the server returns manipulated content or headers.'}, {'type': 'list_item', 'content': 'curl "http://targetsite/includes/pdfstream.php?IMG=1\' UNION SELECT 1,2,3-- -"'}, {'type': 'list_item', 'content': 'curl "http://targetsite/includes/imagestream.php?IMG=1\' UNION SELECT \'Hello Hacker Abi\',null,null-- -"'}, {'type': 'list_item', 'content': 'curl "http://targetsite/includes/anyfilestream.php?IMG=1\' UNION SELECT database(),version(),user()-- -"'}, {'type': 'paragraph', 'content': 'Successful exploitation is indicated by HTTP 200 OK responses with manipulated content-disposition headers or page content reflecting the injected SQL payload.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting or disabling access to the vulnerable PHP scripts (pdfstream.php, imagestream.php, anyfilestream.php) until a patch or fix is applied.
Implement input validation and sanitization on the IMG parameter to prevent SQL injection attacks.
Use prepared statements or parameterized queries in the application code to safely handle user inputs.
Monitor web server logs for suspicious GET requests targeting the vulnerable parameters.
Apply any available security patches or updates from the ownDMS vendor or community.