dbcve.org
Photoshop CcApplication · Adobe

CVE-2019-7989

HIGH · 8.8 CVSS v3.0 Published 2019-08-26
Fix available
A fix is available. Upgrade to after 20.0.5 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable 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
Adobe Photoshop CC versions 19.1.8 and earlier and 20.0.5 and earlier have a command injection vulnerability. Successful exploitation could lead to arbitrary code execution.

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 Photoshop CC versions 19.1.8 and earlier and 20.0.5 and earlier contain a command injection vulnerability that allows attackers to execute arbitrary code through crafted input, likely via file handling or a specific feature that insufficiently sanitizes user-supplied data before passing it to system commands.

MitigationApply the vendor-supplied security update (patch) to upgrade Photoshop CC to a patched version beyond 19.1.8 and 20.0.5; until patched, restrict access to untrusted files and monitor for suspicious behavior.

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
Photoshop CcApplication
Affected:<= 19.1.8>= 20.0, <= 20.0.5

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

CVSS:3.0/AV:N/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. Determine installed Photoshop CC version
    Open Photoshop, go to Help > About Photoshop (or check the application bundle/version info in your OS program manager)
    Affected if The version displayed is 19.1.8 or earlier, OR is 20.0.5 or earlier (20.0.x where x <= 5)
  2. Confirm product is Adobe Photoshop CC
    Verify the installed application is Adobe Photoshop CC (not Photoshop Elements, Lightroom, or other Adobe products)
    Affected if The product is Photoshop CC and version falls within the affected ranges
  3. Check for untrusted file processing capability
    Determine if the system processes image files from untrusted or external sources through Photoshop (e.g., users opening attachments, batch processing external files)
    Affected if Users or automated processes open or process untrusted/crafting-capable files in Photoshop
  4. Review file type handlers
    Check which file formats Photoshop is configured to open by default or has associated handlers for (especially non-standard or legacy formats)
    Affected if Photoshop is set to automatically open files from untrusted locations or has handlers for less common formats that could contain crafted payloads

You are affected if Adobe Photoshop CC version is 19.1.8 or earlier, or 20.0.5 or earlier, and the system processes untrusted files through Photoshop.

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.

From vendor data
Upgrade available Upgrade to a release after 20.0.5
Interim mitigation

Apply the vendor-supplied security update (patch) to upgrade Photoshop CC to a patched version beyond 19.1.8 and 20.0.5; until patched, restrict access to untrusted files and monitor for suspicious behavior.

Fix this in Photoshop Cc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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