CVE-2025-5428

6.3 MEDIUM

📋 TL;DR

This critical vulnerability in juzaweb CMS allows unprivileged users to access and potentially delete error logs through the /admin-cp/log-viewer endpoint due to improper access controls. Attackers can exploit this remotely to view sensitive system information or disrupt logging functionality. All juzaweb CMS installations up to version 3.4.2 are affected.

💻 Affected Systems

Products:
  • juzaweb CMS
Versions: up to 3.4.2
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the Error Logs Page component at /admin-cp/log-viewer. No special configuration required for exploitation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could delete critical error logs to cover tracks after other attacks, view sensitive system information in logs, or potentially chain with other vulnerabilities for further system compromise.

🟠

Likely Case

Unauthorized users accessing error logs containing sensitive information like system paths, configuration details, or user data, potentially enabling reconnaissance for further attacks.

🟢

If Mitigated

With proper access controls, only authorized administrators can view logs, maintaining audit trail integrity and preventing information disclosure.

🌐 Internet-Facing: HIGH - The vulnerability is remotely exploitable and public exploit details exist, making internet-facing instances prime targets.
🏢 Internal Only: MEDIUM - Internal attackers or compromised accounts could exploit this to gather information or cover tracks, though less immediate than external threats.

🎯 Exploit Status

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

Exploit requires some user access (not necessarily admin), but detailed public documentation exists making exploitation straightforward.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None available

Restart Required: No

Instructions:

No official patch available. Vendor was contacted but did not respond. Consider workarounds or alternative CMS solutions.

🔧 Temporary Workarounds

Restrict access to /admin-cp/log-viewer

all

Block or restrict access to the vulnerable endpoint using web server configuration or application firewalls.

# Apache: <Location /admin-cp/log-viewer> Require all denied </Location>
# Nginx: location /admin-cp/log-viewer { deny all; }

Implement authentication middleware

all

Add proper authentication checks before allowing access to log viewer functionality.

# Modify juzaweb source to check user permissions before serving /admin-cp/log-viewer

🧯 If You Can't Patch

  • Isolate juzaweb CMS instances behind strict network segmentation and firewalls
  • Implement comprehensive logging and monitoring for unauthorized access attempts to /admin-cp/log-viewer

🔍 How to Verify

Check if Vulnerable:

Test if non-admin users can access http://[your-domain]/admin-cp/log-viewer and view or delete error logs.

Check Version:

Check juzaweb version in admin panel or configuration files

Verify Fix Applied:

Verify that only authenticated administrators can access /admin-cp/log-viewer and that proper access controls are enforced.

📡 Detection & Monitoring

Log Indicators:

  • Unauthorized access attempts to /admin-cp/log-viewer
  • Unexpected log deletion events
  • Access from non-admin user accounts to log endpoints

Network Indicators:

  • HTTP requests to /admin-cp/log-viewer from unauthorized IPs or users
  • Unusual patterns of log-related API calls

SIEM Query:

source="web_logs" AND (uri="/admin-cp/log-viewer" AND user_role!="admin") OR (event="log_deletion" AND user_role!="admin")

🔗 References

📤 Share & Export