CVE-2025-7594
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-7594 is a critical SQL injection vulnerability in the Job Diary 1.0 application, specifically in the /view-emp.php file. The vulnerability occurs because the 'id' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, data leakage, data modification or deletion, full system compromise, and potential service disruption. Attackers can exploit it remotely without authentication, threatening the confidentiality, integrity, and availability of the affected system 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 /view-emp.php endpoint with SQL injection payloads targeting the 'id' parameter. Tools like sqlmap can be used to automate detection. Example command: sqlmap -u "http://<target>/job-diary-master/view-emp.php?id=1" --batch --level=5 --risk=3. Manual testing can include injecting payloads such as 'id=1 OR 1=1' or time-based payloads like 'id=1 AND (SELECT SLEEP(5))' to observe delays or errors indicating SQL injection. [3, 2]
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) Implementing prepared statements with parameter binding to prevent SQL injection. 3) Applying 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 the application database connection. 5) Conducting regular security audits to detect and fix vulnerabilities promptly. [3, 2, 1]