CVE-2019-25709
Unauthorized Database Access and Deletion in CF Image Hosting
Publication date: 2026-04-12
Last updated on: 2026-04-23
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| codefuture | image_hosting_script | 1.6.5 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-552 | The product makes files or directories accessible to unauthorized actors, even though they should not be. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2019-25709 affects CF Image Hosting Script version 1.6.5 and allows unauthenticated attackers to download the application's database file named imgdb.db from the upload/data directory without any authentication.
This database file is base64 encoded and contains serialized PHP data. Attackers can decode and unserialize this data to extract delete IDs stored in plaintext.
Using these delete IDs, attackers can send requests to the application with the d parameter to delete any picture hosted on the platform, effectively allowing unauthorized deletion of all pictures.
How can this vulnerability impact me? :
This vulnerability can have a severe impact as it allows attackers to delete all pictures hosted on the CF Image Hosting Script platform without any authentication.
The unauthorized access to the database and deletion of images compromises the availability and integrity of the hosted content.
Because the delete IDs are stored in plaintext and the database file is publicly accessible, attackers can easily exploit this to cause data loss and disrupt service.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if the database file imgdb.db is publicly accessible without authentication at the path /upload/data/imgdb.db on the target system.
A basic detection method involves attempting to download the imgdb.db file using commands like curl or wget to see if it is accessible.
- curl http://<target-url>/upload/data/imgdb.db -o imgdb.db
- wget http://<target-url>/upload/data/imgdb.db
If the file is accessible, you can decode its base64 content and unserialize the data using tools or scripts (e.g., Python with phpserialize library) to extract delete IDs, which confirms the vulnerability.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting public access to the imgdb.db database file by applying proper access controls on the /upload/data/ directory.
Ensure that the database file is not directly accessible via the web server by configuring the server to deny access or move the database file outside the web root.
Implement authentication and authorization checks to prevent unauthenticated users from accessing sensitive files or performing deletion operations.
Review and update the application to avoid storing sensitive delete IDs in plaintext and to validate requests that trigger deletion.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthenticated attackers to access and download the application database containing sensitive information such as delete IDs stored in plaintext. This unauthorized access and potential manipulation of data can lead to breaches of confidentiality, integrity, and availability of user data.
Such unauthorized access and data manipulation could negatively impact compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal data and ensuring data integrity and availability.
However, the provided context and resources do not explicitly mention the impact on compliance with these standards.