CVE-2020-11719: An issue was discovered in Programi Bilanc build 007 release 014 31.01.2020 and possibly below

Q: How do I fix CVE-2020-11719?

bilanc: upgrade to newer than 014_31.01.2020. Exact commands for each OS are on this page.

Q: Is CVE-2020-11719 being exploited?

CVE-2020-11719 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-11719 affect?

CVE-2020-11719 affects bilanc. Severity is high (CVSS 7.5). An issue was discovered in Programi Bilanc build 007 release 014 31.01.2020 and possibly below. It relies on broken encryption with a weak and guessable static encryption key.

Q: How urgent is CVE-2020-11719?

Priority 47/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADE

CVE-2020-11719 is a high-severity flaw (CVSS 7.5) affecting bilanc. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue was discovered in Programi Bilanc build 007 release 014 31.01.2020 and possibly below. It relies on broken encryption with a weak and guessable static encryption key.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.0% (top 37%)
CISA exploited list	No
Weakness	CWE-798
Published	2020-12-23
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: bilanc

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-12-23 17:15 UTCPublished CVE record published
2026-06-17 02:50 UTCUpdated Record last modified

bilanc bilanc UPGRADE

Affected: <= 014_31.01.2020

Fixed in: newer than 014_31.01.2020

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy bilanc || rpm -q bilanc || bilanc --version

2. UPGRADE to newer than 014_31.01.2020 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade bilanc

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade bilanc

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-11719?

bilanc: upgrade to newer than 014_31.01.2020. Exact commands for each OS are on this page.

Is CVE-2020-11719 being exploited?

CVE-2020-11719 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-11719 affect?

CVE-2020-11719 affects bilanc. Severity is high (CVSS 7.5). An issue was discovered in Programi Bilanc build 007 release 014 31.01.2020 and possibly below. It relies on broken encryption with a weak and guessable static encryption key.

How urgent is CVE-2020-11719?

Priority 47/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2020-8995 CRITICAL 9.8 UPGRADE Programi Bilanc Build 007 Release 014 31.01.2020 supplies a .exe file containing several hardcoded credentials
CVE-2020-11720 CRITICAL 9.8 UPGRADE An issue was discovered in Programi Bilanc build 007 release 014 31.01.2020 and possibly below
CVE-2020-11718 HIGH 7.4 UPGRADE An issue was discovered in Programi Bilanc build 007 release 014 31.01.2020 and below
CVE-2020-11717 CRITICAL 9.8 UPGRADE An issue was discovered in Programi 014 31.01.2020

References

← Back to latest CVEs