dbcve.org
DreamweaverApplication · Adobe

CVE-2026-47907

HIGH · 8.6 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 21.8 or later.
See remediation →
89/100
Remediation priority · High
No privileges

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
Dreamweaver Desktop versions 21.7 and earlier are affected by an Improper Access Control vulnerability that could result in arbitrary code execution in the context of the current user. An attacker could exploit this vulnerability to execute arbitrary code. Exploitation of this issue requires user interaction in that a victim must open a malicious file. Scope is changed.

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

Adobe Dreamweaver Desktop versions 21.7 and earlier contain an Improper Access Control vulnerability that allows arbitrary code execution in the context of the current user. Exploitation requires the victim to open a malicious file, making social engineering a likely attack vector. The CVSS scope change indicates the vulnerability impacts components beyond the original vulnerable component.

MitigationUpdate Dreamweaver to a version newer than 21.7. Avoid opening untrusted or unexpected files in Dreamweaver until the patch is applied.

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
DreamweaverApplication
Affected:< 21.8

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Dreamweaver installation
    Search for Dreamweaver executable or check common installation paths (e.g., C:\Program Files\Adobe\Adobe Dreamweaver [year] or /Applications/Adobe Dreamweaver on macOS). Also check the Windows Registry under HKLM\SOFTWARE\Adobe\Dreamweaver or use system tools like 'wmic product' or 'Get-WmiObject -Class Win32_Product' on Windows, or 'ls /Applications' on macOS.
    Affected if Dreamweaver is installed on the system
  2. Determine installed Dreamweaver version
    Right-click the Dreamweaver executable and select 'Properties' > 'Details', or open Dreamweaver and go to Help > About Adobe Dreamweaver, or check the Windows Registry under HKLM\SOFTWARE\Adobe\Dreamweaver\InstallPath\Version
    Affected if The version displayed is 21.7 or earlier (any version below 21.8)
  3. Check Dreamweaver file handling behavior
    Review Dreamweaver's Site Setup or File Association settings (Edit > Preferences > File Types / File Associations) to see which file extensions are configured to open automatically in Dreamweaver. Inspect recent file access logs if available.
    Affected if Dreamweaver is configured to automatically open files from untrusted or external locations without user confirmation prompts
  4. Inspect related configuration files
    Look for Dreamweaver configuration files in the user profile (e.g., %APPDATA%\Adobe\Dreamweaver\en_US\Configuration or ~/Library/Application Support/Adobe/Dreamweaver/). Check for any recently modified config files that may indicate tampering or unexpected settings.
    Affected if Configuration files show unusual settings or recently modified files that could indicate exploitation attempts

A user is affected if Adobe Dreamweaver version 21.7 or earlier is installed, as this version contains the improper access control vulnerability that allows arbitrary code execution via malicious file opening.

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
Upgrade available Upgrade to 21.8 or later
Fixed in 21.8
Interim mitigation

Update Dreamweaver to a version newer than 21.7. Avoid opening untrusted or unexpected files in Dreamweaver until the patch is applied.

Recommended fix High confidence

21.8 or later

  1. Open Adobe Creative Cloud desktop application or navigate to the Adobe Dreamweaver download page at helpx.adobe.com
  2. Locate Adobe Dreamweaver in your installed applications
  3. Check the current installed version to confirm it is below 21.8
  4. Initiate the update or download Dreamweaver version 21.8 or later
  5. Complete the installation process following the on-screen prompts
  6. Restart Dreamweaver and verify the version shows 21.8 or later

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

Fix this in Dreamweaver Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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