CVE-2025-10744 is a vulnerability classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) affecting the WordPress plugin 'File Manager, Code Editor, and Backup by Managefy' developed by softdiscover. This vulnerability exists in all versions up to and including 1.6.1 and arises due to publicly accessible log files that contain sensitive information such as full filesystem paths and backup file locations. These log files are exposed without authentication, allowing any remote attacker to retrieve them simply by accessing the relevant URLs. The exposure of such information can facilitate attacker reconnaissance, enabling them to map the server's directory structure and identify backup files that might be targeted in subsequent attacks. The CVSS v3.1 base score is 5.3 (medium severity), reflecting that the vulnerability is remotely exploitable over the network without authentication or user interaction but only impacts confidentiality, not integrity or availability. No patches or fixes are currently linked, and no known exploits have been reported in the wild as of the publication date (October 1, 2025). The vulnerability's impact is limited to information disclosure, but the disclosed data can be leveraged in multi-stage attacks such as privilege escalation or data exfiltration. The vulnerability affects all versions of the plugin, which is commonly used in WordPress environments for file management, code editing, and backup functionalities.

For European organizations, the exposure of sensitive filesystem paths and backup file locations can significantly increase the risk of targeted attacks. Attackers can use this information to identify critical files, backup locations, or configuration files, which may lead to further exploitation such as privilege escalation, ransomware deployment, or data theft. Organizations relying on WordPress sites with this plugin, especially those hosting sensitive or regulated data, face increased risk of confidentiality breaches. While the vulnerability does not directly affect system integrity or availability, the information disclosed can be a stepping stone for more severe attacks. This is particularly concerning for sectors like finance, healthcare, government, and critical infrastructure in Europe, where data protection regulations such as GDPR impose strict requirements on safeguarding sensitive information. The lack of authentication and user interaction requirements makes the vulnerability easier to exploit remotely, increasing the attack surface for European entities operating public-facing WordPress sites.

1. Immediately restrict access to the exposed log files by configuring web server rules (e.g., .htaccess for Apache, location blocks for Nginx) to deny public access to directories or files containing logs. 2. Monitor and audit web server logs to detect any unauthorized access attempts to log files or backup directories. 3. If possible, disable logging features in the plugin or configure them to store logs outside the web root or in locations not accessible via HTTP. 4. Regularly update the plugin to the latest version once a patch addressing this vulnerability is released by the vendor. 5. Implement a Web Application Firewall (WAF) with rules to block requests targeting known log file paths or suspicious access patterns. 6. Conduct thorough security reviews of WordPress installations to identify and remediate similar exposure issues. 7. Educate site administrators about the risks of exposing sensitive files and the importance of secure plugin configurations. 8. Consider alternative plugins with better security track records if timely patching is not feasible.