dbcve.org
Photo StudioApplication · Acdsee

CVE-2019-15293

HIGH · 7.8 CVSS v3.0 Published 2019-08-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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
An issue was discovered in ACDSee Photo Studio Standard 22.1 Build 1159. There is a User Mode Write AV starting at IDE_ACDStd!IEP_ShowPlugInDialog+0x000000000023d060.

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

A user mode write access violation (AV) vulnerability exists in ACDSee Photo Studio Standard 22.1 Build 1159 within the plugin dialog functionality (IEP_ShowPlugInDialog). This indicates a memory corruption issue where the application writes to an invalid or unintended memory location, potentially leading to arbitrary code execution if exploited with carefully crafted input.

MitigationApply the vendor-supplied patch or upgrade to a patched version of ACDSee Photo Studio. Until patched, restrict access to untrusted image files and disable or limit the plugin functionality.

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
Photo StudioApplication
Affected:= 22.1

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

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/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. Identify installed ACDSee Photo Studio version
    Open ACDSee Photo Studio, go to Help > About or check the program's properties in Control Panel > Programs and Features to locate the version number
    Affected if Version displayed is 22.1 with Build 1159 exactly
  2. Verify the specific build number
    Look for the exact build/version string in the application's About dialog or installation directory's version info - it should read exactly 22.1.1159 or 22.1 Build 1159
    Affected if Build number matches 1159 exactly (version 22.1 but different builds are not affected)
  3. Confirm plugin dialog functionality is present
    In the ACDSee interface, navigate to Tools > Plug-ins or try to access the IEP_ShowPlugInDialog feature through the Plugins/Extensions menu where third-party plugins are managed
    Affected if The plugin management dialog interface exists and is accessible in the application

You are affected only if ACDSee Photo Studio Standard version 22.1 with build 1159 is installed AND the plugin dialog feature is present and accessible in your installation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patch or upgrade to a patched version of ACDSee Photo Studio. Until patched, restrict access to untrusted image files and disable or limit the plugin functionality.

Fix this in Photo Studio Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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