CVE-2025-8923 is a SQL Injection vulnerability identified in version 1.0 of the code-projects Job Diary application. The vulnerability exists in the /edit-details.php file, where the 'ID' parameter is improperly sanitized, allowing an attacker to inject malicious SQL code. This flaw enables remote attackers to manipulate backend database queries without requiring authentication or user interaction. The vulnerability has a CVSS 4.0 base score of 6.9, indicating a medium severity level. The attack vector is network-based (AV:N), with low attack complexity (AC:L), no privileges required (PR:N), and no user interaction needed (UI:N). The impact affects confidentiality, integrity, and availability at a low level (VC:L, VI:L, VA:L). The scope remains unchanged (S:U), and there is a partial exploit code maturity (E:P). Although no known exploits are currently active in the wild, the public disclosure of the vulnerability increases the risk of exploitation. SQL Injection vulnerabilities typically allow attackers to extract sensitive data, modify or delete database contents, and potentially execute administrative operations on the database server, which can lead to data breaches or service disruptions. The lack of authentication requirements and the ability to exploit remotely make this vulnerability particularly concerning for exposed installations of Job Diary 1.0.

For European organizations using code-projects Job Diary 1.0, this vulnerability poses a significant risk to the confidentiality and integrity of their data. Organizations that rely on this application for managing job or project details could face unauthorized data disclosure, data tampering, or even complete database compromise. This could lead to operational disruptions, loss of client trust, regulatory non-compliance (especially under GDPR), and potential financial penalties. Since the vulnerability can be exploited remotely without authentication, any exposed Job Diary installations on public-facing servers are at immediate risk. The medium severity rating suggests that while the impact is serious, it may not lead to full system compromise without additional vulnerabilities or misconfigurations. However, the partial impact on availability could still disrupt business processes. European organizations in sectors such as construction, project management, or any industry using this software for job tracking should be particularly vigilant.

1. Immediate application of patches or updates from the vendor once available is critical. Since no patch links are currently provided, organizations should monitor vendor communications closely. 2. Implement Web Application Firewalls (WAFs) with rules specifically designed to detect and block SQL Injection attempts targeting the /edit-details.php endpoint and the 'ID' parameter. 3. Conduct thorough input validation and sanitization on all user-supplied inputs, especially the 'ID' parameter, using parameterized queries or prepared statements to prevent injection. 4. Restrict direct internet access to the Job Diary application where possible, limiting access to trusted internal networks or VPNs. 5. Perform regular security assessments and code reviews focusing on injection vulnerabilities. 6. Monitor logs for unusual database query patterns or repeated failed attempts to access /edit-details.php with suspicious parameters. 7. Educate development and IT teams about secure coding practices and the risks of SQL Injection. 8. Consider deploying database activity monitoring tools to detect and alert on anomalous queries that could indicate exploitation attempts.