CVE-2020-10539: An issue was discovered in Epikur before 20.1.1

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

epikur: upgrade to 20.1.1. Exact commands for each OS are on this page.

Q: Is CVE-2020-10539 being exploited?

CVE-2020-10539 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-10539 affect?

CVE-2020-10539 affects epikur. Severity is critical (CVSS 9.8). An issue was discovered in Epikur before 20.1.1. The Epikur server contains the checkPasswort() function that, upon user login, checks the submitted password against the user password's MD5 hash stored in the database. It is also compared t

Q: How urgent is CVE-2020-10539?

Priority 63/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2020-10539 is a critical-severity flaw (CVSS 9.8) affecting epikur. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue was discovered in Epikur before 20.1.1. The Epikur server contains the checkPasswort() function that, upon user login, checks the submitted password against the user password's MD5 hash stored in the database. It is also compared to a second MD5 hash, which is the same for every user (aka a "Backdoor Password" of 3p1kursupport). If the submitted password matches either one, access is granted.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.5% (top 26%)
CISA exploited list	No
Weakness	CWE-287
Published	2021-02-05
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: epikur

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

Am I affected?

Timeline

2021-02-05 14:15 UTCPublished CVE record published
2026-06-17 02:47 UTCUpdated Record last modified

epikur epikur UPGRADE

Affected: < 20.1.1

Fixed in: 20.1.1

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 20.1.1 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade epikur

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-10539?

epikur: upgrade to 20.1.1. Exact commands for each OS are on this page.

Is CVE-2020-10539 being exploited?

CVE-2020-10539 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-10539 affect?

CVE-2020-10539 affects epikur. Severity is critical (CVSS 9.8). An issue was discovered in Epikur before 20.1.1. The Epikur server contains the checkPasswort() function that, upon user login, checks the submitted password against the user password's MD5 hash stored in the database. It is also compared t

How urgent is CVE-2020-10539?

Priority 63/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2020-10538 MEDIUM 5.5 UPGRADE An issue was discovered in Epikur before 20.1.1
CVE-2020-10537 HIGH 7.8 UPGRADE An issue was discovered in Epikur before 20.1.1

References

← Back to latest CVEs