CVE-2025-52095
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 · uneditedAn issue in PDQ Smart Deploy V.3.0.2040 allows an attacker to escalate privileges via the Credential encryption routines in SDCommon.dll
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 confidencePDQ Smart Deploy version 3.0.2040 contains a privilege escalation vulnerability in the credential encryption routines of SDCommon.dll, allowing attackers to elevate their privileges through flaws in how credentials are encrypted or handled within the application.
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< 3.0.2046CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Check PDQ Smart Deploy installed versionOpen the application or check Add/Remove Programs for PDQ Smart Deploy and note the installed version numberAffected if The installed version is 3.0.2040 through 3.0.2045 (any version below 3.0.2046)
-
Locate SDCommon.dll fileSearch for SDCommon.dll in the PDQ Smart Deploy installation directory (commonly C:\Program Files\PDQ Deploy or a custom install path)Affected if The file exists and its version is below 3.0.2046, or the file date matches an affected release
-
Verify credential handling is configuredCheck if Smart Deploy is configured with stored credentials for deployment packages, scan profiles, or inventory collectionAffected if The application stores or uses encrypted credentials for any deployment or inventory functionality
You are affected if PDQ Smart Deploy version is below 3.0.2046 and you use credential-based features in the application.
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 · scoped3.0.2046
Contact PDQ for the patched version of Smart Deploy and apply available updates; until then, restrict access to the application and monitor for unauthorized privilege escalation attempts.
3.0.2046
- Navigate to the PDQ Smart Deploy application or the official PDQ download portal
- Locate the PDQ Smart Deploy download for version 3.0.2046 or later
- Download the installer for the updated version
- Close any running instances of PDQ Smart Deploy
- Run the installer and follow the prompts to upgrade the application
- Verify the installation completed successfully by checking the version number in the application
- Restart any services or scheduled tasks that rely on PDQ Smart Deploy
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing6.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 $4,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52095 — 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-52095 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