Skip to main content
CVE-2025-8923VulnerabilityPublished

CVE-2025-8923: code-projects Job Diary · SQL Injection

Affects code-projects Job DiarySource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
code-projects Job DiaryAffected
  • =1.0
Fixed in–

AI-suggested

1. Immediate application of patches or updates from the vendor once available is critical. 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.

Description

A vulnerability was determined in code-projects Job Diary 1.0. This vulnerability affects unknown code of the file /edit-details.php. The manipulation of the argument ID leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…