CVE-2020-23560
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 · uneditedIrfanView 4.54 allows a user-mode write access violation starting at FORMATS!ShowPlugInSaveOptions_W+0x000000000001bcab.
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 confidenceIrfanView 4.54 contains a user-mode write access violation vulnerability in the FORMATS plugin module at function ShowPlugInSaveOptions_W. This indicates a memory corruption issue, likely exploitable via a specially crafted image file processed by the affected plugin, leading to potential arbitrary code execution.
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= 4.54CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check IrfanView versionOpen IrfanView and go to Help > About, or right-click the executable and view Properties > Details to see the version numberAffected if Version is exactly 4.54
-
Locate the FORMATS pluginNavigate to the IrfanView 'Plugins' folder (typically C:\Program Files\IrfanView\Plugins or C:\Program Files (x86)\IrfanView\Plugins) and look for FORMATSDLL files such as formats.dll, i_es.dll, or other format-specific plugin DLLsAffected if FORMATS plugin DLL exists in the Plugins folder on version 4.54
-
Verify plugin is loaded and functionalIn IrfanView, try opening or processing an image file (especially formats handled by plugins like JPEG2000, RAW, or other extended formats) to confirm plugin functionality is activeAffected if Plugins load and process images on IrfanView 4.54
-
Check for Save Plug-In Options capabilityIn IrfanView, go to Image > Save Advanced or right-click a loaded image and look for plugin-related save options that invoke the ShowPlugInSaveOptions_W functionAffected if Plugin save options are accessible in the affected version
You are affected if IrfanView version 4.54 is installed and the FORMATS plugin module is present and functional.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedUpgrade IrfanView to the latest version beyond 4.54 to obtain the vendor patch. Avoid opening untrusted image files with vulnerable plugin functionality until patched.
IrfanView 4.57 or latest available version
- 1. Navigate to the official IrfanView website at www.irfanview.com
- 2. Download the latest version of IrfanView (version 4.57 or later recommended)
- 3. Uninstall the current version 4.54 from your system
- 4. Install the newly downloaded latest version
- 5. Verify the installation was successful by launching IrfanView
- 6. Confirm the vulnerability is resolved by testing image viewing and plugin functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-23560 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-23560 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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