CVE-2025-0934

6.3 MEDIUM

📋 TL;DR

This SQL injection vulnerability in Job Recruitment 1.0 allows remote attackers to execute arbitrary SQL commands via the 'n' parameter in /parse/_call_job_search_ajax.php. Organizations using this software for job recruitment systems are affected. The vulnerability enables unauthorized database access and potential data manipulation.

💻 Affected Systems

Products:
  • code-projects Job Recruitment
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all installations of version 1.0 with the vulnerable file present.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including theft of sensitive applicant data, credential harvesting, and potential system takeover via subsequent attacks.

🟠

Likely Case

Data exfiltration of job applications, user information, and potential privilege escalation within the application.

🟢

If Mitigated

Limited impact with proper input validation and database permissions restricting damage to non-sensitive data.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Public exploit documentation available via GitHub repository. SQL injection is a well-understood attack vector with many automated tools available.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://code-projects.org/

Restart Required: No

Instructions:

No official patch available. Consider migrating to alternative software or implementing custom fixes with proper input validation and parameterized queries.

🔧 Temporary Workarounds

Input Validation Filter

all

Add server-side validation to sanitize the 'n' parameter before processing

Modify /parse/_call_job_search_ajax.php to validate and sanitize input

Web Application Firewall Rule

all

Block SQL injection patterns targeting the vulnerable endpoint

WAF rule: Block requests to /parse/_call_job_search_ajax.php containing SQL keywords in 'n' parameter

🧯 If You Can't Patch

  • Restrict network access to the application using firewall rules
  • Implement database user with minimal necessary permissions

🔍 How to Verify

Check if Vulnerable:

Check if file /parse/_call_job_search_ajax.php exists and contains unsanitized 'n' parameter usage in SQL queries

Check Version:

Check software version in admin panel or configuration files

Verify Fix Applied:

Test with SQL injection payloads (e.g., ' OR '1'='1) in the 'n' parameter and verify no database errors or unexpected results

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL errors in application logs
  • Multiple rapid requests to /parse/_call_job_search_ajax.php with varying 'n' parameters

Network Indicators:

  • HTTP POST requests to vulnerable endpoint containing SQL keywords (SELECT, UNION, etc.)

SIEM Query:

source="web_logs" AND uri="/parse/_call_job_search_ajax.php" AND (param_n CONTAINS "UNION" OR param_n CONTAINS "SELECT" OR param_n CONTAINS "OR 1=1")

🔗 References

📤 Share & Export