CVE-2025-7593
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-7593 is a critical SQL injection vulnerability in the Job Diary 1.0 application, specifically in the /view-all.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 lead to unauthorized database access, data leakage, data modification, and deletion. Attackers can exploit it remotely without authentication, potentially compromising the confidentiality, integrity, and availability of your system. It may also lead to full system compromise or service disruption, posing a serious threat to system security 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-all.php file for SQL injection using various techniques such as boolean-based blind, error-based, and time-based blind SQL injection. Example payloads include: - Boolean-based blind: id=(SELECT (CASE WHEN (5051=5051) THEN 1 ELSE (SELECT 2621 UNION SELECT 2885) END)) - Error-based: id=1 OR (SELECT 1063 FROM(SELECT COUNT(*),CONCAT(0x7162716a71,(SELECT (ELT(1063=1063,1))),0x716b7a71,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a) - Time-based blind: id=1 AND (SELECT 7447 FROM (SELECT(SLEEP(5)))NXRC) Testing can be automated using tools like sqlmap against the URL, for example: sqlmap -u "http://<target>/job-diary-master/view-all.php?id=1" --batch These methods help confirm if the 'id' parameter is vulnerable to SQL injection. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1. Use prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2. Implement strict input validation and filtering to ensure inputs conform to expected formats. 3. Minimize database user permissions, avoiding use of high-privilege accounts like 'root' or 'admin' for application database access. 4. Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly. If possible, consider replacing the affected software with an alternative product as no known mitigations are documented. [2, 3]