CVE-2025-10744 json
File Manager, Code editor, backup by Managefy <= 1.6.1 - Unauthenticated Information Exposure
published last yr. modified last mo. also EUVD-2025-31820
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2025-10744 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- softdiscover File Manager, Code Editor, and Backup by Managefy
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/30147e39-af94-4620-870b-71a0a46b7509?source=cve
- plugins.trac.wordpress.org /browser/softdiscover-db-file-manager/tags/1.5.0/modules/filemanager/helpers/iprogress.php#L19
- plugins.trac.wordpress.org /browser/softdiscover-db-file-manager/tags/1.5.0/modules/filemanager/controllers/backup.php#L460
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3369101%40softdiscover-db-file-manager&new=3369101%40softdiscov
Sources
- CVE List CVE-2025-10744
- NVD CVE-2025-10744
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.