Skip to main content
VulnerabilityPublished Updated

CVE-2025-54256: Adobe Dreamweaver Desktop · Cross-Site Request Forgery (CSRF)

Affects Adobe Dreamweaver DesktopSource CVE Database V5

0

Not known to be exploited · CVSS 8.6 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Adobe Dreamweaver DesktopAffected
  • =0
Fixed in–

AI-suggested

To mitigate CVE-2025-54256 effectively, organizations should: 1) Immediately update Adobe Dreamweaver Desktop to the latest version once a patch is released by Adobe, as no patches are currently available. 2) Implement strict email and web filtering to reduce the risk of users receiving or clicking malicious links that could trigger CSRF attacks. 3) Educate users about the risks of clicking on unsolicited or suspicious links, emphasizing the specific threat posed by this vulnerability. 4) Employ application whitelisting and endpoint protection solutions to detect and block unauthorized code execution attempts within Dreamweaver. 5) Use network segmentation to limit the exposure of development environments to external networks and reduce the blast radius of potential compromises. 6) Monitor logs and system behavior for unusual activities related to Dreamweaver processes or unexpected file modifications. 7) Consider disabling or restricting Dreamweaver’s network access temporarily if feasible until a patch is available. 8) Review and enhance CSRF protections in internal web applications and development tools to prevent similar vulnerabilities. These targeted actions go beyond generic advice and address the specific exploitation vector and environment of this vulnerability.

Description

Dreamweaver Desktop versions 21.5 and earlier are affected by a Cross-Site Request Forgery (CSRF) vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must click on a malicious link, and scope is changed.

References

Community reviews

Loading reviews…