CVE-2025-7595
BaseFortify
Publication date: 2025-07-14
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| anisha | job_diary | 1.0 |
Helpful Resources
Exploitability
| 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. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-7595 is a critical SQL injection vulnerability in the Job Diary 1.0 application, specifically in the /view-cad.php file. It occurs because the 'id' parameter from HTTP GET requests is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This flaw enables attackers to manipulate SQL queries sent to the database, potentially retrieving, modifying, or deleting sensitive data without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive data, modification or deletion of data, full system control by attackers, and service interruptions. Since it can be exploited remotely without authentication, it poses a significant threat to system security, data integrity, and business continuity. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'id' parameter in the /view-cad.php file for SQL injection flaws. Tools like sqlmap can be used to automate detection. For example, running sqlmap with the URL parameter 'id=1' can help identify the vulnerability. Additionally, attackers may be identified by monitoring for unusual or malicious SQL queries targeting the 'id' parameter. Google dorking with the query "inurl:view-cad.php" can help identify vulnerable targets externally. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected software with an alternative product if possible. 2) Applying prepared statements with parameter binding to separate SQL code from user input, preventing injection. 3) Implementing strict input validation and filtering on the 'id' parameter to ensure it conforms to expected formats. 4) Minimizing database user permissions by avoiding high-privilege accounts for routine operations. 5) Conducting regular security audits to detect and fix vulnerabilities promptly. [1, 3, 2]