CVE-2025-0818

6.5 MEDIUM

📋 TL;DR

This CVE describes a directory traversal vulnerability in elFinder versions 2.1.64 and prior when used in WordPress plugins. Unauthenticated attackers can delete arbitrary files if a site owner has explicitly made the file manager available to users. WordPress sites using vulnerable elFinder-based plugins are affected.

💻 Affected Systems

Products:
  • WordPress plugins using elFinder library
Versions: elFinder 2.1.64 and prior
Operating Systems: All
Default Config Vulnerable: ✅ No
Notes: Vulnerability only exploitable if site owner explicitly enables file manager access to users

⚠️ 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 site compromise through deletion of critical WordPress files (wp-config.php, .htaccess), leading to site defacement, data loss, or privilege escalation.

🟠

Likely Case

Selective file deletion causing site functionality disruption, content removal, or configuration corruption requiring restoration from backups.

🟢

If Mitigated

No impact if file manager is not exposed to users or proper access controls are implemented.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: LOW

🎯 Exploit Status

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

Exploitation requires the file manager to be accessible to users, which is not the default configuration

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: elFinder 2.1.65+

Vendor Advisory: https://github.com/Studio-42/elFinder

Restart Required: No

Instructions:

1. Update all WordPress plugins using elFinder to versions containing elFinder 2.1.65 or later. 2. Check plugin changelogs for security updates. 3. Update plugins via WordPress admin panel or manually replace elFinder files.

🔧 Temporary Workarounds

Disable user-accessible file manager

all

Remove or restrict access to the file manager interface from user-facing areas of the site

Implement file access controls

all

Add authentication and authorization checks before allowing file operations

🧯 If You Can't Patch

  • Disable or remove vulnerable plugins entirely
  • Implement web application firewall rules to block directory traversal patterns

🔍 How to Verify

Check if Vulnerable:

Check WordPress plugin directories for elFinder.class.php files and examine version information in file headers or changelogs

Check Version:

grep -r 'elFinder' /path/to/wordpress/wp-content/plugins/ | grep -i version

Verify Fix Applied:

Confirm elFinder version is 2.1.65 or later by checking file headers or plugin documentation

📡 Detection & Monitoring

Log Indicators:

  • Unusual file deletion requests
  • Directory traversal patterns in URLs (../ sequences)
  • Requests to file manager endpoints from unauthenticated users

Network Indicators:

  • HTTP requests containing '../' patterns to file manager endpoints
  • DELETE or POST requests to file operations endpoints

SIEM Query:

source="web_logs" AND (uri="*../*" OR method="DELETE") AND uri="*elfinder*"

🔗 References

📤 Share & Export