dbcve.org
Sensitive Information in LogsWeakness · CWE-532

CVE-2025-10645

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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 WP Reset plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.05 via the WF_Licensing::log() method when debugging is enabled (default). This makes it possible for unauthenticated attackers to extract sensitive license key and site data.

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 WP Reset WordPress plugin versions up to 2.05 expose sensitive information through the WF_Licensing::log() method when debugging is enabled (the default setting). This method logs license keys and site data to an accessible location, allowing unauthenticated attackers to retrieve this sensitive information.

MitigationUpdate WP Reset to version 2.06 or later, or disable the debug logging feature if an update is not immediately possible. Additionally, rotate any license keys that may have been exposed.

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 WP Reset plugin is installed and identify its version
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Reset' in the list. The version number is displayed below the plugin name. Alternatively, check the plugin file header in /wp-content/plugins/wp-reset/wp-reset.php for the 'Version' comment.
    Affected if The installed version is 2.05 or earlier (any version up to and including 2.05).
  2. Verify whether debug logging is enabled in WP Reset settings
    Navigate to WP Reset > Tools in the WordPress admin panel. Look for a 'Debug' or 'Debugging' setting. Since the default setting enables debugging, check if it has been explicitly disabled. If you cannot access the admin, check the wp_options table for option_name containing 'wp_reset_debug' or 'wf_debug' with a value of '1' or 'true'.
    Affected if Debug logging is enabled (this is the default setting in affected versions).
  3. Inspect accessible log files for exposed license keys and site data
    Check the following locations for log files: /wp-content/wpr-logs/, /wp-content/debug.log (if WP_DEBUG_LOG is enabled), and any files matching *license*.log or *debug*.log in /wp-content/. Use a file manager or command line (ls -la, find) to list these files. Open any found log files and search for license key strings, API keys, or 'WF_Licensing' method calls.
    Affected if Log files exist in accessible web directories and contain license keys, site data, or entries from the WF_Licensing::log() method.

You are affected if WP Reset version 2.05 or earlier is installed, debug logging is enabled (the default), and accessible log files contain license keys or sensitive licensing data from WF_Licensing.

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

Update WP Reset to version 2.06 or later, or disable the debug logging feature if an update is not immediately possible. Additionally, rotate any license keys that may have been exposed.

Recommended fix Moderate confidence

WP Reset version 2.06 or later

  1. Upgrade the WP Reset plugin to version 2.06 or later from the WordPress plugin repository
  2. As a temporary mitigation before upgrading, disable plugin debugging by setting WP_DEBUG to false in wp-config.php
  3. Verify that debugging is disabled by checking that the wp-content/debug.log file is not being written with sensitive license data

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10645 — 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-10645 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