CVE-2019-7956
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 · uneditedAdobe Dreamweaver direct download installer versions 19.0 and below, 18.0 and below have an Insecure Library Loading (DLL hijacking) vulnerability. Successful exploitation could lead to Privilege Escalation in the context of the current user.
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 confidenceAdobe Dreamweaver installer versions 19.0 and below and 18.0 and below are vulnerable to DLL hijacking, where the installer loads dynamic link libraries from untrusted paths. An attacker with local access can place a malicious DLL in a location where the installer searches for libraries, achieving privilege escalation to the current user's privilege level.
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<= 19.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 installed Dreamweaver versionOpen Programs and Features or use command 'reg query "HKLM\SOFTWARE\Adobe\Dreamweaver" /v Version' to find the installed version numberAffected if The installed version is 19.0 or below, meaning it falls within the affected version range
-
Verify Dreamweaver installer presenceSearch for Dreamweaver installer files (.exe, .msi) in common download or installation directories such as the user's Downloads folder or temporary directoriesAffected if Installer files exist in world-writable or untrusted directories where an attacker could place malicious DLLs
-
Inspect installer directories for unauthorized DLLsExamine the folders containing Dreamweaver installer executables for unexpected or recently added DLL files that are not part of the official installer packageAffected if Unknown DLL files are present in directories where the installer loads libraries
-
Check for DLL search order hijacking opportunitiesReview the installer directory permissions and verify if any folder in the DLL search path is writable by non-admin usersAffected if Installer directories are writable by standard users, allowing DLL placement by local attackers
A system is affected if Dreamweaver version 19.0 or below is installed and the installer or its directories are accessible to untrusted users who could place malicious DLLs.
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.
From vendor dataApply vendor-provided patches from Adobe for Dreamweaver installer versions. As an interim control, ensure the installer runs from trusted locations only and monitor for unauthorized DLL placement in installer directories.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7956 — 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-2019-7956 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