dbcve.org
SnagitApplication · Techsmith

CVE-2020-11541

MEDIUM · 5.5 CVSS v3.1 Published 2020-05-08
Fix available
A fix is available. Upgrade to after 20.0.3 or later.
See remediation →
57/100
Remediation priority · Elevated
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
In TechSmith SnagIt 11.2.1 through 20.0.3, an XML External Entity (XXE) injection issue exists that would allow a local attacker to exfiltrate data under the local Administrator account.

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

An XML External Entity (XXE) injection vulnerability in TechSmith SnagIt versions 11.2.1 through 20.0.3 allows a local attacker to craft malicious XML files that, when processed by the application, can read files and exfiltrate data from the local Administrator account context.

MitigationUpgrade to a SnagIt version newer than 20.0.3 when available; as a compensating control, restrict local system access to trusted users and monitor for unusual XML file processing by the SnagIt application.

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
SnagitApplication
Affected:>= 11.2.1, <= 20.0.3

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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. Confirm SnagIt installation
    Look for SnagIt in the installed programs list (Control Panel > Programs and Features) or check for the installation directory at C:\Program Files\TechSmith\SnagIt
    Affected if SnagIt is present on the system
  2. Determine installed SnagIt version
    Right-click SnagIt.exe in the installation directory and select Properties > Details to view the File Version, or check the version shown in Help > About SnagIt within the application
    Affected if Installed version is 11.2.1 or higher and 20.0.3 or lower
  3. Confirm XML file processing capability
    Identify whether SnagIt is used to process or import XML files, as this vulnerability is triggered when the application parses malicious XML input
    Affected if SnagIt processes XML files and the installed version falls within the vulnerable range 11.2.1 to 20.0.3

A system is affected by this CVE if SnagIt is installed with a version between 11.2.1 and 20.0.3 inclusive and the application processes XML files.

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.3
Interim mitigation

Upgrade to a SnagIt version newer than 20.0.3 when available; as a compensating control, restrict local system access to trusted users and monitor for unusual XML file processing by the SnagIt application.

Fix this in Snagit Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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