Information Disclosure in File Manager, Code Editor, and Backup by Managefy (WordPress plugin) (CVE-2025-10744)
Summary
Vulnerability in File Manager, Code Editor, and Backup by Managefy (WordPress plugin) (CVE-2025-10744). Confidential information can be exposed externally.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-10744 has been found in File Manager, Code Editor, and Backup by Managefy (WordPress plugin).
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "File Manager, Code Editor, and Backup by Managefy (WordPress plugin) CVE-2025-10744" on the vendor's site.
CVE-2025-10744 (File Manager, Code Editor, and Backup by Managefy (WordPress plugin)) — CWE-200 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in File Manager, Code Editor, and Backup by Managefy (WordPress plugin).
Check the vendor advisory for the affected versions of File Manager, Code Editor, and Backup by Managefy (WordPress plugin).
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで File Manager, Code Editor, and Backup by Managefy (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。