CVE-2023-1681

4.3 MEDIUM

📋 TL;DR

This vulnerability in Xunrui CMS 4.61 allows remote attackers to access sensitive information through the /config/myfield/test.php file. It affects all systems running the vulnerable version of Xunrui CMS. The information disclosure could expose configuration data or other sensitive details.

💻 Affected Systems

Products:
  • Xunrui CMS
Versions: 4.61
Operating Systems: All platforms running Xunrui CMS
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability exists in a specific file path that appears to be part of the CMS configuration system.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers obtain sensitive configuration data, database credentials, or system information leading to further compromise.

🟠

Likely Case

Unauthorized access to configuration files revealing system paths, settings, or other non-critical information.

🟢

If Mitigated

Limited exposure of non-sensitive information with proper access controls and monitoring.

🌐 Internet-Facing: HIGH - Remote exploitation possible without authentication.
🏢 Internal Only: MEDIUM - Internal attackers could still exploit but requires network access.

🎯 Exploit Status

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

Exploit details are publicly available on GitHub, making this easy to weaponize.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None found

Restart Required: No

Instructions:

No official patch available. Consider upgrading to a newer version if available or implementing workarounds.

🔧 Temporary Workarounds

Remove vulnerable file

linux

Delete or restrict access to the vulnerable test.php file

rm /config/myfield/test.php
chmod 000 /config/myfield/test.php

Access restriction

all

Block access to the vulnerable path using web server configuration

# Apache: <Location "/config/myfield/test.php"> Require all denied </Location>
# Nginx: location ~ /config/myfield/test\.php { deny all; }

🧯 If You Can't Patch

  • Implement strict network access controls to limit who can reach the CMS
  • Deploy WAF rules to block requests to /config/myfield/test.php

🔍 How to Verify

Check if Vulnerable:

Check if /config/myfield/test.php exists and is accessible via HTTP request

Check Version:

Check CMS version in admin panel or configuration files

Verify Fix Applied:

Verify the file is no longer accessible via HTTP requests

📡 Detection & Monitoring

Log Indicators:

  • HTTP requests to /config/myfield/test.php
  • Unusual access patterns to configuration directories

Network Indicators:

  • HTTP GET requests to /config/myfield/test.php

SIEM Query:

url.path:"/config/myfield/test.php" AND http.method:GET

🔗 References

📤 Share & Export