CVE-2025-11446
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 · uneditedInsertion of Sensitive Information into Log File vulnerability in upKeeper Solutions upKeeper Manager allows Use of Known Domain Credentials.This issue affects upKeeper Manager: from 5.2.0 before 5.2.12.
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 · moderate confidenceThe vulnerability allows insertion of sensitive information into log files in upKeeper Manager versions 5.2.0 through 5.2.11, potentially exposing domain credentials. An attacker with access to the log files could obtain these credentials and use them for further compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 5.0.0, < 5.2.13.1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed upKeeper Manager versionCheck the version of upKeeper Manager installed in your environment. This is typically found in the application UI under Help > About, or by checking the installation directory for a version file or manifest.Affected if The installed version is >= 5.0.0 and < 5.2.13.1
-
Locate upKeeper Manager log filesIdentify the directory where upKeeper Manager stores its log files. Common locations include the installation directory or a logs subfolder within the application data directory.Affected if Log files exist and the application version is within the affected range
-
Inspect log files for credentialsSearch through the log files for patterns that may indicate exposed credentials, such as password parameters, authentication tokens, or domain/Active Directory credential strings. Look for keywords like 'password', 'credential', 'domain', or base64-encoded strings that may represent credentials.Affected if Log files contain any plaintext or encoded credentials, password values, or authentication tokens that should not be logged
-
Verify credential exposure scopeReview all log files created during the timeframe when the affected version was in use. Determine if any domain credentials, user passwords, or authentication tokens are present in the logs.Affected if Any domain credentials or authentication secrets are found in the log files
Your environment is affected if upKeeper Manager version is 5.0.0 through 5.2.11 (or < 5.2.13.1) AND domain credentials or authentication tokens are present in the application log files.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.2.13.1
Upgrade upKeeper Manager to version 5.2.12 or later. Review existing log files for any exposed credentials and rotate any potentially compromised credentials.
5.2.13.1 or later
- 1. Obtain the latest version of upKeeper Manager (5.2.13.1 or later) from the official vendor source (support.upkeeper.se)
- 2. Review the vendor's upgrade documentation for upKeeper Manager
- 3. Create a backup of the current upKeeper Manager configuration and database
- 4. Test the upgrade in a non-production environment before deploying to production
- 5. Execute the upgrade following the vendor's documented procedure
- 6. Verify the upgrade was successful and confirm the new version is 5.2.13.1 or later
- 7. Review log files to confirm sensitive information is no longer being written to logs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11446 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11446 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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