CVE-2020-13878 is a critical (CVSS 9.8) heap based out of bounds write in the B3D plugin for IrfanView, at offset +27ef in B3d.dll. IrfanView B3D PlugIns before 4.56 are affected. Update the plugin pack to 4.56 or later, or remove the plugin if you do not open B3D files.
What's affected
- IrfanView B3D PlugIns before version 4.56, per the record.
- The researcher write-up for a sibling report in this group says the flaw is in the plugin, not in IrfanView itself, and cites IrfanView 4.54 plugins as tested.
- Fixed: 4.56, per the record and the IrfanView version history cited by the write-up.
The record scores it 9.8 (Critical) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. The record does not flag it as a CISA Known Exploited Vulnerability, and none of the pages I read report exploitation in the wild.
How to check if you're exposed
Open IrfanView, choose Help, then About IrfanView, and check the plugin list, or look at the file version of B3D.dll in your Plugins folder through file properties. Anything older than 4.56 is in range.
What to do now
- Find machines that run IrfanView, including portable copies on shared drives.
- Check the plugin pack version.
- Install the IrfanView plugin pack at 4.56 or later from the official IrfanView site.
- If you cannot update, delete B3d.dll from the Plugins folder, since few users need B3D files.
- Do not open 3D model files from untrusted sources until the plugin is fixed.
After you patch, record the new version for IrfanView B3D plugin in your asset inventory, and confirm it with the same check you used above. A fix that was never verified is easy to forget, and an inventory that shows versions is what lets you answer the next advisory in minutes instead of days.
Why it matters
The record maps the flaw to CWE-787, out of bounds write. A parser in a plugin writes past the end of a heap buffer while reading a file, which can corrupt memory. Memory corruption bugs in file parsers are a common route to code execution, and the record scores this 9.8, but it does not describe a working attack, and this post does not either.
The score assumes a user opens a crafted file, so the practical control is to keep untrusted files away from the viewer and keep plugins current. This is one of three B3D entries filed separately, each at a different code location: CVE-2020-13878, CVE-2020-13879 and CVE-2020-13880. The fix version is the same.
To check open source components in your own projects for known CVEs like this one, try the free in-browser dependency scan at gold.safeguard.sh/scan, or look the CVE up in the Gold directory.
Quick check
Do I need the main IrfanView update too?
The record and write-up point at the B3D plugin, which ships in the plugin pack. Update the plugin pack to 4.56 or later and check the IrfanView download page for any other release notes.
How do I find every place IrfanView B3D plugin is used?
Start with an inventory of installed software and versions, because you cannot patch what you have not found. Check servers, build hosts, test copies and anything a vendor bundles. For open source libraries, a dependency scan or SBOM gives the same list for your code.
Sources
Last reviewed: 19 October 2026.