CVE-2024-50843

5.3 MEDIUM

📋 TL;DR

This vulnerability allows remote attackers to view directory listings in PHPGurukul User Registration & Login and User Management System 3.2 via the /loginsystem/assets path. This exposes sensitive files and directory structures to unauthorized users. Organizations using this specific version of the PHPGurukul system are affected.

💻 Affected Systems

Products:
  • PHPGurukul User Registration & Login and User Management System
Versions: 3.2
Operating Systems: Any OS running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects systems with the vulnerable version installed and accessible via web.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could discover and download sensitive configuration files, database backups, or credential files leading to full system compromise.

🟠

Likely Case

Attackers enumerate directory contents to find additional attack vectors, sensitive information, or misconfigured files.

🟢

If Mitigated

Directory listing is disabled, limiting information disclosure to known file paths only.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires only web browser access to the vulnerable path.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None known

Restart Required: No

Instructions:

No official patch available. Apply workarounds or upgrade to a newer version if available.

🔧 Temporary Workarounds

Disable Directory Listing

all

Configure web server to prevent directory listing for the vulnerable path.

For Apache: Add 'Options -Indexes' to .htaccess in /loginsystem/assets directory
For Nginx: Add 'autoindex off;' to server block configuration

Restrict Access

all

Block access to /loginsystem/assets directory via web server configuration.

For Apache: 'Deny from all' in .htaccess
For Nginx: 'location /loginsystem/assets { deny all; }'

🧯 If You Can't Patch

  • Implement web application firewall rules to block directory listing requests
  • Monitor access logs for requests to /loginsystem/assets path

🔍 How to Verify

Check if Vulnerable:

Navigate to http://[target]/loginsystem/assets/ in a web browser. If directory contents are displayed, system is vulnerable.

Check Version:

Check application version in admin panel or readme files.

Verify Fix Applied:

Attempt to access the same URL after applying fixes. Should return 403 Forbidden or similar error instead of directory listing.

📡 Detection & Monitoring

Log Indicators:

  • HTTP 200 responses to GET requests for /loginsystem/assets/
  • Multiple sequential requests to /loginsystem/assets/* paths

Network Indicators:

  • Unusual traffic patterns to /loginsystem/assets directory

SIEM Query:

source="web_logs" AND uri_path="/loginsystem/assets/" AND status=200

🔗 References

📤 Share & Export