dbcve.org
DreamweaverApplication · Adobe

CVE-2024-30314

HIGH · 7.8 CVSS v3.1 Published 2024-05-16
Fix available
A fix is available. Upgrade to 21.4 or later.
See remediation →
81/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.3 and earlier are affected by an Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability that could lead in arbitrary code execution by an attacker. Exploitation of this issue does require user interaction.

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 confidence

Adobe Dreamweaver Desktop versions 21.3 and earlier contain an OS Command Injection vulnerability that allows attackers to execute arbitrary code on the targeted system. Successful exploitation requires user interaction, likely in the form of a malicious file or action within the application.

MitigationUpdate Dreamweaver to a version newer than 21.3 to remediate this vulnerability. Until patched, limit user interactions with untrusted files or remote resources.

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.4

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/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 checks

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

  1. Verify Dreamweaver is installed
    On Windows, check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Dreamweaver or look in C:\Program Files\Adobe\Adobe Dreamweaver. On macOS, check /Applications/Adobe Dreamweaver.
    Affected if Dreamweaver application is present on the system
  2. Identify installed Dreamweaver version
    Open Dreamweaver and go to Help > About Adobe Dreamweaver, or on Windows check the registry value Version in HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Dreamweaver, or on macOS right-click Dreamweaver in Applications and select Get Info to view the version number.
    Affected if Version cannot be determined or is lower than 21.4
  3. Compare version against affected range
    Note the full version number (for example, 21.3, 21.2, 21.1) and compare it to the affected range of versions earlier than 21.4.
    Affected if Installed version is 21.3, 21.2, 21.1, or any earlier version (any version less than 21.4)
  4. Assess user interaction exposure
    Determine if the Dreamweaver installation is used to work with untrusted web files, remote server connections, or files from external sources, as exploitation requires user interaction with malicious content.
    Affected if Running an affected version AND regularly handling untrusted files or remote resources within Dreamweaver

You are affected if Adobe Dreamweaver Desktop is installed with any version earlier than 21.4, and that version interacts with untrusted files or remote resources.

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.4 or later
Fixed in 21.4
Interim mitigation

Update Dreamweaver to a version newer than 21.3 to remediate this vulnerability. Until patched, limit user interactions with untrusted files or remote resources.

Recommended fix High confidence

Dreamweaver 21.4

  1. Verify current Dreamweaver version by launching Dreamweaver and navigating to Help > About Adobe Dreamweaver
  2. Close Dreamweaver completely before upgrading
  3. Download Adobe Dreamweaver version 21.4 or later from the official Adobe website (helpx.adobe.com) or through the Creative Cloud desktop application
  4. Run the installer and follow the on-screen prompts to complete the upgrade
  5. Launch Dreamweaver after installation completes and verify the version shows 21.4 or later via Help > About Adobe Dreamweaver

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-2024-30314 — 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-2024-30314 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