dbcve.org
XnviewApplication

CVE-2019-17261

HIGH · 7.8 CVSS v3.1 Published 2019-10-08
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
XnView Classic 2.49.1 allows a User Mode Write AV starting at Xwsq+0x0000000000001e51.

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

XnView Classic 2.49.1 contains a User Mode Write Access Violation vulnerability in the Xwsq component. This indicates a memory corruption issue where the application attempts to write to an invalid memory address, potentially triggered by processing a specially crafted file.

MitigationUpgrade to a patched version of XnView Classic when available, or implement compensating controls such as restricting file processing from untrusted sources and deploying endpoint detection solutions.

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
XnviewApplication
Affected:= 2.49.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.1/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 XnView Classic version
    Open XnView Classic, go to Help > About, or right-click the executable and view Properties > Details to see the product version
    Affected if The version displayed is 2.49.1 exactly
  2. Locate Xwsq component files
    Search the XnView installation directory for files with .xwsq extension or xwsq-related DLLs/plugins
    Affected if Xwsq files or related components exist in the installation folder
  3. Check for recent Xwsq file processing
    Review the application usage logs if enabled, or check the recent documents/file history on the system for .xwsq files processed by XnView
    Affected if The user or system has processed .xwsq files using XnView Classic
  4. Verify file association handling
    Check Windows file associations (Registry under HKCR\.xwsq) to see if XnView is registered to open Xwsq files
    Affected if XnView Classic is set as the default handler for .xwsq files and users open such files

You are affected if XnView Classic version 2.49.1 is installed and the Xwsq component is present and actively used to process Xwsq files, as the vulnerability is triggered by specially crafted Xwsq 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of XnView Classic when available, or implement compensating controls such as restricting file processing from untrusted sources and deploying endpoint detection solutions.

Fix this in Xnview Scoped from the published advisory
  • Consultation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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