What is the CVSS score of EUVD-2025-21333?

EUVD-2025-21333 has a CVSS 4.0 base score of 5.5 (Medium). CVSS vector: 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. EPSS exploitation probability: 0.0%.

Is there a public PoC exploit available for EUVD-2025-21333?

Yes, a public proof-of-concept exploit is available for EUVD-2025-21333. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate EUVD-2025-21333?

Within 24 hours: Inventory all systems running Job Diary 1.0 and restrict network access to /view-cad.php via firewall rules. Within 7 days: Deploy Web Application Firewall (WAF) rules to block SQL injection patterns targeting the ID parameter, and implement input validation if accessible. Within 30 days: Plan migration to a patched version or alternative solution when vendor releases a security update, or consider decommissioning the application if business-critical.

Job Diary EUVD-2025-21333

| CVE-2025-7595 MEDIUM

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') (CWE-74)

2025-07-14 cna@vuldb.com

PHP SQLi Job Diary Anisha

5.5

CVSS 4.0 · NVD

View

Vulnerability Assessment

Weakness	CWE CWE-74 OWASP Top 10:2025 A05:2025 - Injection ASVS 5.0 V1 - Encoding and Sanitization Input neutralization, injection prevention
Impact	Risk is HIGH in real-world environments. CVSS 7.3 reflects High severity due to: (1) AV:N (network-accessible), (2) AC:L (no attack complexity), (3) PR:N (no authentication required), (4) UI:N (no user interaction needed), and (5) impact on confidentiality, integrity, and availability. Public POC disclosure significantly increases exploitation probability (likely EPSS > 0.80). The combination of unauthenticated access, low technical barriers, and database-level impact makes this immediately exploitable by script kiddies and automated scanners. This is NOT a low-real-risk scenario—it represents genuine critical infrastructure risk for any deployed instances. The discrepancy between 'critical' designation and 7.3 CVSS suggests the 7.3 may be conservative (database compromise is typically 8.0+).
Exploit ScenarioDerived	An attacker performs reconnaissance and identifies a Job Diary 1.0 instance via banner grabbing or directory enumeration. They craft a malicious URL: `http://target.com/view-cad.php?ID=1' OR '1'='1` to test for SQL injection. Upon confirmation, they execute: `http://target.com/view-cad.php?ID=1' UNION SELECT database(),user(),version()--` to extract database credentials, then escalate to data exfiltration (e.g., SELECT * FROM users INTO OUTFILE) or data destruction. No authentication is required, no user interaction is needed, and the attack succeeds in seconds using standard SQL injection payloads available in public tools (sqlmap, Burp Suite). A fully automated attack chain (discovery → exploitation → exfiltration) is feasible.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).

No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAI

A critical SQL injection vulnerability exists in code-projects Job Diary 1.0 via the ID parameter in /view-cad.php, allowing unauthenticated remote attackers to execute arbitrary SQL commands and potentially extract, modify, or delete database contents. The vulnerability has been publicly disclosed with proof-of-concept code available, and while the CVSS score is 7.3 (High), the unauthenticated attack vector and low complexity suggest active exploitation is likely. No patch has been confirmed available as of this analysis.

RemediationAI

{'type': 'Primary', 'action': 'Apply vendor patch or upgrade', 'details': 'Contact code-projects for patched version > 1.0. Check project repository (if public) for security updates. Upgrade immediately if patch is available.'} {'type': 'Immediate (Pre-Patch)', 'action': 'Implement parameterized queries', 'details': "Modify /view-cad.php to use prepared statements (mysqli prepared statements or PDO with bound parameters) for all SQL queries involving the ID parameter. Example: $stmt = $mysqli->prepare('SELECT * FROM table WHERE ID = ?'); $stmt->bind_param('i', $_GET['ID']); $stmt->execute();"} {'type': 'Input Validation', 'action': 'Whitelist ID parameter format', 'details': "If ID is numeric, enforce integer-only validation: if (!ctype_digit($_GET['ID'])) { exit('Invalid ID'); }. Validate against expected data types before any database operation."} {'type': 'Network Segmentation', 'action': 'Restrict access to Job Diary', 'details': 'Place application behind WAF or IP whitelist. Disable /view-cad.php access if not currently required.'} {'type': 'Database Hardening', 'action': 'Principle of least privilege', 'details': 'Ensure database user running Job Diary queries has minimal required permissions. Disable statement-level backup/restore capabilities if possible.'}

Affected VersionsENISA

Job Diary 1.0

Affected Packages

euvd job_diary no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Job Diary 1.0 is a PHP-based web application (CPE likely: cpe:2.3:a:code-projects:job_diary:1.0:*:*:*:*:*:*:*). The vulnerability stems from CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component, 'Injection'), specifically SQL injection (CWE-89). The /view-cad.php endpoint fails to properly sanitize or parameterize the ID parameter before incorporating it into SQL queries. This is a classic first-order SQL injection vulnerability where user-supplied input is directly concatenated into SQL statements without using prepared statements or proper input validation.

Know when Job Diary gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 5.5 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Lifecycle Timeline

Severity Changed

Apr 29, 2026 - 01:11 NVD

HIGH MEDIUM

CVSS changed

Apr 29, 2026 - 01:11 NVD

7.3 (HIGH) 5.5 (MEDIUM)

PoC Detected

Jul 15, 2025 - 18:27 vuln.today

Public exploit code

CVE Published

Jul 14, 2025 - 11:15 nvd

HIGH 7.3

DescriptionCVE.org

A vulnerability was found in code-projects Job Diary 1.0. It has been declared as critical. This vulnerability affects unknown code of the file /view-cad.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.

Executive ViewAI

Why It Matters

A critical SQL injection vulnerability in Job Diary 1.0 allows remote attackers to compromise database integrity and potentially exfiltrate sensitive data without authentication. With public exploits already available and no patch currently available, this poses an immediate risk to any organization using this application.

Business Impact: Severe

Compensating Controls

Implement WAF rules blocking SQL injection payloads in the ID parameter; restrict network access to /view-cad.php to authorized users only via firewall; disable the affected functionality if not business-critical; monitor database access logs for suspicious queries; consider disabling the application until patched if data sensitivity is high.

Threat Intelligence Overview

EPSS Score

0.0%

Top 87% exploitable

Exploit

POC

Public exploit code exists

Data Quality

6 sources

Confidence: High

EUVD

NVD

CVE.org

EPSS

GitHub

VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity MEDIUM

CISA KEV No

Public POC Yes

EPSS 0.0%

Patch available No

Active threat No

Deciding rule

MEDIUM severity (CVSS 4.0-6.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.