CVE-2025-14568

6.3 MEDIUM

📋 TL;DR

This CVE describes a SQL injection vulnerability in haxxorsid Stock-Management-System that allows remote attackers to execute arbitrary SQL commands via manipulation of employee_id/id/admin parameters in the User.php file. The vulnerability affects all versions up to commit fbbbf213e9c93b87183a3891f77e3cc7095f22b0, and the product is no longer maintained by the vendor.

💻 Affected Systems

Products:
  • haxxorsid Stock-Management-System
Versions: All versions up to commit fbbbf213e9c93b87183a3891f77e3cc7095f22b0
Operating Systems: Any OS running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the model/User.php file. The product uses continuous delivery with rolling releases, making specific version tracking difficult.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data manipulation, and potential remote code execution if database permissions allow.

🟠

Likely Case

Unauthorized data access, privilege escalation, and potential data exfiltration from the stock management database.

🟢

If Mitigated

Limited impact with proper input validation and parameterized queries in place.

🌐 Internet-Facing: HIGH - The vulnerability can be exploited remotely and the exploit is publicly available.
🏢 Internal Only: MEDIUM - While exploitable internally, external exposure increases attack surface significantly.

🎯 Exploit Status

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

Exploit details are publicly available in GitHub repositories. Attack requires access to vulnerable endpoints but doesn't require authentication based on the description.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Not available

Vendor Advisory: Not available - vendor did not respond to disclosure

Restart Required: No

Instructions:

No official patch available. Consider migrating to supported software or implementing workarounds.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Implement strict input validation and parameterized queries for all user inputs in User.php

Manual code review and modification of model/User.php

Web Application Firewall Rules

all

Deploy WAF rules to block SQL injection patterns targeting employee_id/id/admin parameters

WAF-specific configuration commands

🧯 If You Can't Patch

  • Isolate the application behind a reverse proxy with strict input filtering
  • Implement network segmentation to limit database access from the application server

🔍 How to Verify

Check if Vulnerable:

Check if your version is at or before commit fbbbf213e9c93b87183a3891f77e3cc7095f22b0 by examining the codebase or version metadata

Check Version:

git log --oneline | head -1 (if using git) or check version files in the application

Verify Fix Applied:

Test SQL injection attempts against the vulnerable endpoints to ensure they are properly sanitized

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in application logs
  • Multiple failed login attempts with SQL-like patterns in parameters

Network Indicators:

  • HTTP requests containing SQL keywords in employee_id/id/admin parameters
  • Unusual database connection patterns

SIEM Query:

source="web_logs" AND ("employee_id" OR "id" OR "admin") AND ("UNION" OR "SELECT" OR "INSERT" OR "DELETE")

🔗 References

📤 Share & Export