dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2025-10560

CRITICAL · 9.3 CVSS v4.0 Published 2026-06-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Worksnaps before version 1.6.20260201 contains hardcoded cloud credentials and related secret material in the Worksnaps client application binaries. The exposed credentials included AWS access keys, S3 bucket names, and related cloud access information. The originally exposed AWS credentials authenticated as the AWS account root identity and provided access to Worksnaps production cloud resources, including S3 buckets containing sensitive data such as screenshots of user desktops. An attacker with access to the affected client binaries could extract or recover the credentials and use them to access affected Worksnaps cloud resources.

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

Worksnaps client binaries contained hardcoded AWS root account credentials including access keys and S3 bucket names. These credentials provided full access to production cloud resources including S3 buckets storing sensitive user desktop screenshots. Attackers could extract these credentials from the client binaries to access the affected cloud resources.

MitigationImmediately rotate all exposed AWS credentials (root access keys and any derived credentials), audit AWS account activity for unauthorized access, implement a secrets management solution to replace hardcoded credentials, and rebuild/re-release the client application without embedded credentials.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify Worksnaps client installation
    Open Windows Programs and Features (or macOS Applications folder) and locate 'Worksnaps' or 'Worksnaps Client'. Note the installed version shown.
    Affected if Worksnaps client is installed with a version earlier than 1.6.20260201
  2. Check executable version properties
    Navigate to the Worksnaps installation directory (commonly C:\Program Files\Worksnaps or C:\Program Files (x86)\Worksnaps on Windows, or /Applications on macOS). Right-click the main executable (often named worksnaps.exe or similar) and select Properties, then view the Details tab to see the File Version.
    Affected if The file version shown is earlier than 1.6.20260201
  3. Verify exact version number against threshold
    Compare the discovered version to the fixed version 1.6.20260201. Any version before this (such as 1.6.x, 1.5.x, 1.0.x, etc.) contains the hardcoded AWS root credentials.
    Affected if Installed version is before 1.6.20260201

If the Worksnaps client version is anything earlier than 1.6.20260201, the environment contains the hardcoded AWS root credentials and S3 bucket exposure described in this CVE.

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

Immediately rotate all exposed AWS credentials (root access keys and any derived credentials), audit AWS account activity for unauthorized access, implement a secrets management solution to replace hardcoded credentials, and rebuild/re-release the client application without embedded credentials.

Recommended fix High confidence

1.6.20260201 or later

  1. Back up any local Worksnaps data or configuration files
  2. Uninstall the current Worksnaps client version
  3. Download Worksnaps client version 1.6.20260201 or later from the official vendor website (www.worksnaps.net)
  4. Install the updated Worksnaps client application
  5. Verify the installation was successful and confirm the application runs without errors

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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