CVE-2025-14193

6.3 MEDIUM

📋 TL;DR

This SQL injection vulnerability in Employee Profile Management System 1.0 allows attackers to manipulate database queries via the per_id parameter in view_personnel.php. Attackers can potentially read, modify, or delete sensitive employee data. Organizations using this specific software version are affected.

💻 Affected Systems

Products:
  • code-projects Employee Profile Management System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects systems with the vulnerable view_personnel.php file accessible.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

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

🟠

Likely Case

Data exfiltration of employee records including personal identifiable information, payroll data, and authentication credentials.

🟢

If Mitigated

Limited information disclosure if database permissions are properly restricted and input validation is implemented elsewhere.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit code is publicly available on GitHub, making this easily exploitable by attackers with basic SQL injection knowledge.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

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

Restart Required: No

Instructions:

1. Check vendor website for updates 2. If no patch available, implement workarounds 3. Consider replacing with alternative software

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Add parameter validation to ensure per_id contains only expected values

Modify view_personnel.php to validate per_id parameter using is_numeric() or similar functions

Web Application Firewall Rules

all

Block SQL injection patterns targeting the per_id parameter

Add WAF rule: deny requests containing SQL keywords in per_id parameter

🧯 If You Can't Patch

  • Restrict access to view_personnel.php using IP whitelisting or authentication
  • Implement database-level protections: use least privilege accounts, enable query logging

🔍 How to Verify

Check if Vulnerable:

Test view_personnel.php with SQL injection payloads in per_id parameter (e.g., ' OR '1'='1)

Check Version:

Check software version in admin panel or configuration files

Verify Fix Applied:

Verify that SQL injection payloads no longer execute and return appropriate error messages

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL errors in application logs
  • Multiple requests to view_personnel.php with suspicious parameters

Network Indicators:

  • HTTP requests containing SQL keywords in per_id parameter
  • Unusual database query patterns

SIEM Query:

source="web_logs" AND uri="/view_personnel.php" AND (param="per_id" AND value MATCHES "(?i)(union|select|insert|delete|update|drop|or|and)")

🔗 References

📤 Share & Export