Skip to main content

Job Diary CVE-2025-7533

| EUVDEUVD-2025-21262 MEDIUM
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') (CWE-74)
2025-07-13 cna@vuldb.com
5.5
CVSS 4.0 · NVD
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Input neutralization, injection prevention
Impact

While the CVSS v3.1 score of 7.3 rates this as High severity with full network accessibility (AV:N), low attack complexity (AC:L), no privilege requirements (PR:N), and no user interaction (UI:N), the real-world risk is CRITICAL due to multiple amplifying factors: (1) Public exploit disclosure exists with POC code available, dramatically reducing exploitation barrier; (2) SQL injection against unauthenticated endpoints typically yields full database compromise (confidentiality, integrity, availability all impacted - C:L/I:L/A:L understates actual risk); (3) No patch availability indicated suggests affected organizations have limited remediation options; (4) The attack surface is a common parameter (job_id) that will be discovered and exploited rapidly. EPSS score would likely be elevated (>0.90) given public POC and disclosure. SSVC analysis indicates: exploitation=PoC exists (active), automatable=yes (SQL injection is easily scripted), technical impact=total (database compromise). This transitions from theoretical risk to immediate operational priority requiring emergency response regardless of 7.3 CVSS scoring.

Exploit ScenarioDerived

An attacker performs reconnaissance and identifies a public Job Diary 1.0 installation via banner grabbing or directory enumeration. The attacker crafts a URL like: http://target.com/view-details.php?job_id=1' UNION SELECT version(),user(),database(),4,5--+ which exploits the SQL injection to extract MySQL version and database user information. Upon confirmation of the vulnerability, the attacker escalates to exfiltrate entire database tables containing sensitive job data, applicant information, or credentials by injecting: job_id=1' UNION SELECT GROUP_CONCAT(column_name),2,3,4,5 FROM information_schema.columns WHERE table_schema=database()--+ . Since no authentication is required (PR:N) and attack complexity is low (AC:L), this can be executed manually in seconds or automated via SQLmap. The public POC makes this accessible to both skilled attackers and script kiddies, likely resulting in rapid database compromise across multiple vulnerable installations.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.1% exploitation probability (EPSS)

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

Alert me

AnalysisAI

CVE-2025-7533 is a SQL injection vulnerability in code-projects Job Diary 1.0 affecting the /view-details.php file through the job_id parameter, allowing unauthenticated remote attackers to execute arbitrary SQL queries and potentially read, modify, or delete database contents. The vulnerability has a CVSS score of 7.3 (High) with public exploit disclosure and proof-of-concept availability, indicating active exploitation risk in the wild. This is a critical severity issue for all deployments of the affected version with direct database access implications.

RemediationAI

Immediate actions: (1) PATCH: Upgrade to a patched version if available from code-projects; check vendor repository/website for security updates beyond 1.0 (no specific patch version identified in current intelligence - urgent vendor contact required); (2) WORKAROUND: Implement Web Application Firewall (WAF) rules blocking SQL injection patterns in job_id parameter (e.g., block single quotes, SQL keywords like UNION, OR 1=1, comment syntax); (3) MITIGATION: Restrict network access to /view-details.php via IP allowlisting or require authentication at network/application layer; (4) DETECTION: Monitor database query logs for unusual SQL patterns; enable SQL error logging to catch injection attempts; (5) CODE FIX (interim): Modify /view-details.php to use prepared statements with parameterized queries instead of string concatenation - replace any code using sprintf() or string concatenation with mysqli_prepare() or PDO prepared statements. Example: Use $stmt = $mysqli->prepare('SELECT * FROM jobs WHERE job_id = ?'); $stmt->bind_param('i', $job_id); instead of $query = 'SELECT * FROM jobs WHERE job_id = ' . $_GET['job_id'];

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

The vulnerability is rooted in CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component - 'Injection'), specifically SQL injection within a PHP-based web application. The /view-details.php endpoint fails to properly sanitize or parameterize the job_id parameter before using it in SQL queries, allowing attackers to inject malicious SQL syntax. This is a classic input validation failure where user-controlled data is concatenated directly into SQL statements without prepared statements or input escaping. The affected product is code-projects Job Diary version 1.0, a PHP-based job management application that likely stores job records in a SQL database (MySQL/MariaDB typical for PHP applications). The lack of prepared statement usage or input validation on a commonly-used identifier parameter (job_id) suggests the application was developed without security-first practices.

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

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

4
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 16, 2025 - 14:55 vuln.today
Public exploit code
CVE Published
Jul 13, 2025 - 17:15 nvd
HIGH 7.3

DescriptionCVE.org

A vulnerability was found in code-projects Job Diary 1.0 and classified as critical. This issue affects some unknown processing of the file /view-details.php. The manipulation of the argument job_id leads to sql injection. The attack may 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 unauthenticated remote attackers to compromise database integrity and extract sensitive data. This poses immediate risk to any organization running this application, particularly affecting data confidentiality, integrity, and availability of job records and associated business data.

Business Impact: High
Compensating Controls

Deploy WAF rules to detect and block SQL injection patterns in job_id parameter; implement network segmentation to restrict access to Job Diary application; disable /view-details.php endpoint if not critical to operations; apply strict input validation and parameterized queries in application if source code modification is possible; monitor database logs for suspicious queries; consider disabling the affected application entirely until patch is released.

Threat Intelligence Overview

EPSS Score
0.1%
Top 83% exploitable
Exploit
POC
Public exploit code exists
Data Quality
6 sources
Confidence: High

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.1%
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.

SSVC AssessmentENISA

SSVC Decision· derived
Out-of-Cycle
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

48
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy