Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
AC:L overrides vendor AC:H because WordPress plugin log paths are predictable and enumerable; C:H retained because exposed paths enable unauthenticated retrieval of backup archives containing full database credentials.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
3DescriptionCVE.org
The File Manager, Code Editor, and Backup by Managefy plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.6.1 through publicly exposed log files. This makes it possible for unauthenticated attackers to view information like full paths and full paths to backup files information contained in the exposed log files.
AnalysisAI
Sensitive information exposure in the File Manager, Code Editor, and Backup by Managefy WordPress plugin (all versions ≤1.6.1) allows unauthenticated remote attackers to read publicly accessible log files containing full server-side filesystem paths and backup archive locations. Disclosure of backup file paths is not merely an information leak - if those backup archives are stored within the web root (the default behavior for such plugins), an attacker can directly download the backup and extract a full WordPress database dump including credentials and wp-config.php secrets, escalating the impact well beyond the nominal CWE-200 classification. No public exploit identified at time of analysis; EPSS sits at 0.05% (17th percentile), reflecting limited observed exploitation pressure.
Technical ContextAI
The plugin (WordPress repository slug: softdiscover-db-file-manager, affected through version 1.6.1 per EUVD-2025-31820) exposes operational log files written by two components: the backup controller (backup.php, line 460) and a progress-tracking helper (iprogress.php, line 19). Both components write log entries - including full server-side filesystem paths - to files stored within the plugin's web-accessible directory without any HTTP access restriction. CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) is the root cause class: the application places sensitive operational artifacts in a location reachable by unauthenticated HTTP clients. The failure is architectural - the plugin does not restrict direct HTTP access to its log directory, nor does it use a nonce or authentication check before serving log content.
RemediationAI
Update the File Manager, Code Editor, and Backup by Managefy plugin to a version beyond 1.6.1 - an upstream fix is referenced in WordPress plugin repository changeset 3369101 (https://plugins.trac.wordpress.org/changeset?reponame=&old=3369101%40softdiscover-db-file-manager&new=3369101%40softdiscover-db-file-manager); however, a specific patched release version was not independently confirmed in the available data and should be verified in the WordPress plugin dashboard or repository before updating. As an immediate compensating control, add a web server directive to deny direct HTTP access to the plugin log directory - for Apache, place a Deny from all directive in an .htaccess file under wp-content/plugins/softdiscover-db-file-manager/, and for Nginx, add a location block matching that path with return 403. As a secondary measure, reconfigure the plugin's backup storage destination to a directory outside the web root, which eliminates the risk of backup archive retrieval even if log paths are exposed. Consult the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/30147e39-af94-4620-870b-71a0a46b7509 for any additional vendor-recommended mitigations. Upstream fix available (PR/commit); released patched version not independently confirmed.
The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para
The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r
Same weakness CWE-200 – Information Exposure
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2025-31820