CVE-2025-55128

6.5 MEDIUM

📋 TL;DR

An uncontrolled resource consumption vulnerability in userlog-index.php allows authenticated admin users to request arbitrarily large page sizes, potentially causing denial of service through excessive resource consumption. This affects systems running vulnerable versions of the software with admin interface access.

💻 Affected Systems

Products:
  • Software containing userlog-index.php (specific product name not provided in CVE)
Versions: All versions containing the vulnerable userlog-index.php file
Operating Systems: All operating systems running the vulnerable software
Default Config Vulnerable: ⚠️ Yes
Notes: Requires admin interface access; vulnerability exists in the page size parameter handling.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system unavailability due to resource exhaustion (CPU, memory, or disk I/O) from repeated large requests, potentially affecting all users and services on the same host.

🟠

Likely Case

Performance degradation or temporary service interruption for the affected application, with recovery possible after attack stops or system restart.

🟢

If Mitigated

Minimal impact with proper rate limiting, input validation, and resource quotas in place.

🌐 Internet-Facing: MEDIUM - Requires admin authentication but could be exploited if admin credentials are compromised or through other attack vectors.
🏢 Internal Only: MEDIUM - Internal attackers with admin access could disrupt services, but requires authenticated access to the admin interface.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires admin credentials but is technically simple - just sending requests with large 'items per page' values.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown - check vendor advisory

Vendor Advisory: https://hackerone.com/reports/3413890

Restart Required: No

Instructions:

1. Review the HackerOne report for vendor response. 2. Check for official patches from the software vendor. 3. Apply patches following vendor instructions. 4. Test in non-production environment first.

🔧 Temporary Workarounds

Implement Input Validation

all

Add server-side validation to limit the maximum items per page parameter

Modify userlog-index.php to validate and limit the 'items_per_page' parameter to a reasonable maximum (e.g., 1000)

Rate Limiting

all

Implement rate limiting on admin endpoints to prevent rapid repeated requests

Configure web server or application rate limiting for admin paths

🧯 If You Can't Patch

  • Restrict admin interface access to trusted IP addresses only
  • Implement web application firewall rules to block requests with excessive page size parameters

🔍 How to Verify

Check if Vulnerable:

Test by accessing userlog-index.php with admin credentials and attempting to request an extremely large number of items per page (e.g., 1000000). Monitor system resources during test.

Check Version:

Check software version through admin interface or configuration files specific to the application

Verify Fix Applied:

After applying fixes, repeat the test and verify that large page size requests are rejected or limited, and system resources remain stable.

📡 Detection & Monitoring

Log Indicators:

  • Unusually large 'items_per_page' values in access logs
  • Repeated requests to userlog-index.php from same admin user
  • Error logs showing resource exhaustion warnings

Network Indicators:

  • High volume of requests to admin endpoints
  • Unusual traffic patterns to userlog-index.php

SIEM Query:

source="web_logs" AND uri="*userlog-index.php*" AND (items_per_page>1000 OR parameter_value>1000)

🔗 References

📤 Share & Export