CVE-2025-60076
📋 TL;DR
This CVE describes a PHP Local File Inclusion vulnerability in the Ray Enterprise Translation WordPress plugin. Attackers can exploit improper filename control in include/require statements to read sensitive files on the server. All WordPress sites using affected versions of the lingotek-translation plugin are vulnerable.
💻 Affected Systems
- Ray Enterprise Translation (lingotek-translation WordPress plugin)
⚠️ 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.
- Review the CVE details at NVD
- Check vendor security advisories for your specific version
- Test if the vulnerability is exploitable in your environment
- Consider updating to the latest version as a precaution
⚠️ Risk & Real-World Impact
Worst Case
Full server compromise via reading sensitive files like /etc/passwd, database credentials, or session files, potentially leading to remote code execution.
Likely Case
Information disclosure of sensitive server files, configuration files, or source code, which could enable further attacks.
If Mitigated
Limited impact with proper file permissions and web server restrictions preventing access to sensitive directories.
🎯 Exploit Status
Simple path traversal or file inclusion attacks can exploit this vulnerability without authentication.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Version after 1.7.1
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Plugins. 3. Find 'Ray Enterprise Translation'. 4. Check for updates. 5. Update to latest version. 6. Verify plugin version is >1.7.1.
🔧 Temporary Workarounds
Disable vulnerable plugin
allTemporarily disable the Ray Enterprise Translation plugin until patched
wp plugin deactivate lingotek-translation
Restrict PHP file inclusion
linuxConfigure PHP to disable allow_url_include and restrict open_basedir
allow_url_include = Off
open_basedir = /var/www/html
🧯 If You Can't Patch
- Implement web application firewall (WAF) rules to block file inclusion patterns
- Apply strict file permissions and disable directory listing on web server
🔍 How to Verify
Check if Vulnerable:
Check WordPress plugin version via admin panel or wp-cli: wp plugin list | grep lingotek-translationCheck Version:
wp plugin get lingotek-translation --field=versionVerify Fix Applied:
Confirm plugin version is >1.7.1 and test file inclusion attempts return errors📡 Detection & Monitoring
Log Indicators:
- Unusual file path requests in access logs
- PHP include/require errors with suspicious paths
- Requests containing '../' or file inclusion patterns
Network Indicators:
- HTTP requests with file inclusion parameters
- Unusual file extensions in URLs
SIEM Query:
source="web_access_logs" AND (uri="*../*" OR uri="*php://*" OR uri="*file=*" OR uri="*include=*")