CVE-2025-7593VulnerabilityPublished 14 Jul 2025Updated 15 Jul 2025

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

Affects code-projects Job DiarySource CVE Database V5

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 40% 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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubyihaofuweng/cve`pkg:github/yihaofuweng/cve`Other threats	Affected =1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Given the lack of an official patch, European organizations should immediately implement the following mitigations: 1) Restrict external access to the /view-all.php endpoint by implementing network-level controls such as firewalls or VPNs to limit access to trusted internal users only. 2) Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the 'ID' parameter. 3) Conduct thorough input validation and sanitization on all user-supplied data, especially the 'ID' parameter, to prevent injection attacks. 4) Monitor application logs for suspicious query patterns or repeated access attempts to the vulnerable endpoint. 5) Plan for an urgent update or patch deployment once the vendor releases a fix. 6) Consider isolating or replacing the affected application if it is critical and cannot be secured promptly. 7) Educate development and security teams about secure coding practices to prevent similar vulnerabilities in future releases.

Description

A vulnerability was found in code-projects Job Diary 1.0 and classified as critical. Affected by this issue is some unknown functionality of the file /view-all.php. The manipulation of the argument ID leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using code-projects Job Diary 1.0, this vulnerability poses a risk of unauthorized access to sensitive business data, including potentially personal or operational information stored within the application. Exploitation could lead to data breaches, data tampering, or service disruption, which may result in regulatory non-compliance under GDPR due to unauthorized data exposure. The remote and unauthenticated nature of the attack vector increases the likelihood of exploitation, especially if the application is exposed to the internet. This could impact organizations relying on Job Diary for project tracking or employee management, leading to operational disruptions and reputational damage. Additionally, if the compromised data includes personal employee or client information, the organization could face legal and financial penalties under European data protection laws.

Summary

CVE-2025-7593 is a SQL Injection vulnerability identified in version 1.0 of the code-projects Job Diary application. The flaw exists in the /view-all.php file, specifically in the handling of the 'ID' parameter. An attacker can manipulate this parameter to inject malicious SQL code, which the application then executes on the backend database. This vulnerability is exploitable remotely without requiring authentication or user interaction, making it a significant risk. The injection can lead to unauthorized data access, modification, or deletion, potentially compromising the confidentiality, integrity, and availability of the application's data. The vulnerability has been publicly disclosed, but no known exploits are currently reported in the wild. The CVSS 4.0 base score is 6.9, indicating a medium severity level, reflecting the ease of exploitation (network accessible, no privileges needed) but limited impact scope (low to medium impact on confidentiality, integrity, and availability). The absence of a patch or mitigation guidance in the provided data suggests that affected users must implement their own protective measures until an official fix is released.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Jul 2025, 20:59 UTC

Technical details

References

Community reviews

Related threats