CVE-2025-7533

| EUVD-2025-21262 HIGH
2025-07-13 [email protected]
7.3
CVSS 3.1
Share

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

Lifecycle Timeline

4
Analysis Generated
Mar 16, 2026 - 09:18 vuln.today
EUVD ID Assigned
Mar 16, 2026 - 09:18 euvd
EUVD-2025-21262
PoC Detected
Jul 16, 2025 - 14:55 vuln.today
Public exploit code
CVE Published
Jul 13, 2025 - 17:15 nvd
HIGH 7.3

DescriptionNVD

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.

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.

Technical ContextAI

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.

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'];

Share

CVE-2025-7533 vulnerability details – vuln.today

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