dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-10744

MEDIUM · 5.9 CVSS v3.1 Published 2025-10-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Managefy WordPress plugin (versions up to 1.6.1) stores log files in a publicly accessible location within the web root. Unauthenticated attackers can directly request these log files to retrieve sensitive information including server full paths and backup file paths.

MitigationMove log files outside the web root or restrict access via web server configuration (e.g., .htaccess rules) to prevent unauthenticated access. Verify all log files are inaccessible via HTTP.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Managefy plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'Managefy', or inspect /wp-content/plugins/ directory for a folder named 'managefy' or similar. Check the plugin file headers for version number.
    Affected if The plugin is installed and the version is 1.6.1 or lower
  2. Locate log files created by Managefy
    Search the wp-content/plugins/managefy directory and adjacent directories for files with .log extension, or files named 'debug.log', 'error.log', 'managefy.log', or similar patterns. Also check wp-content/ and the plugin directory itself.
    Affected if Log files exist in any directory within the web root
  3. Test HTTP access to identified log files
    Attempt to directly request each identified log file via browser or curl (e.g., curl -I https://yourdomain.com/wp-content/plugins/managefy/debug.log). A successful 200 OK response indicates public accessibility.
    Affected if Log files return HTTP 200 status and are downloadable without authentication
  4. Verify log file permissions
    Check file system permissions on log files. If they are world-readable (chmod 644 or higher) and located inside the web-accessible document root, they can be fetched by unauthenticated users.
    Affected if Log files have world-readable permissions and reside under the document root

If Managefy plugin version 1.6.1 or lower is installed and its log files are accessible via HTTP requests without authentication, the environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Move log files outside the web root or restrict access via web server configuration (e.g., .htaccess rules) to prevent unauthenticated access. Verify all log files are inaccessible via HTTP.

Recommended fix Moderate confidence

Plugin version higher than 1.6.1 (check WordPress plugin repository for exact latest version)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'File Manager, Code Editor, and Backup by Managefy' plugin
  4. 4. Check the current installed version (should be 1.6.1 or below)
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. Verify the update was successful and the plugin is now running a version higher than 1.6.1

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10744 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10744 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data