CVE-2018-16160: SecureCore Standard Edition Version 2.x allows an attacker to bypass the product 's authentication to log in t

Routine

HIGH 7.8UPGRADE

CVE-2018-16160 is a high-severity flaw (CVSS 7.8) affecting securecore. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

SecureCore Standard Edition Version 2.x allows an attacker to bypass the product 's authentication to log in to a Windows PC.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 73%)
CISA exploited list	No
Weakness	CWE-287
Published	2018-11-15
Last modified	2026-06-17

Publisher (CNA): JPCERT/CC · Vendor: ftsafe

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

Am I affected?

Timeline

2018-11-15 15:29 UTCPublished CVE record published
2026-06-17 01:43 UTCUpdated Record last modified

ftsafe securecore UPGRADE

Affected: >= 2.0 and < 3.0

Fixed in: 3.0

Safe to downgrade to: a release before 2.0

1. Check installed version

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

2. UPGRADE to 3.0 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade securecore

Note

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

3. If no update is available yet, DOWNGRADE to a release before 2.0 (Debian / Ubuntu)

apt-cache madison securecore sudo apt install securecore=<VERSION_BEFORE_2.0> sudo apt-mark hold securecore

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list securecore sudo dnf downgrade securecore-<VERSION_BEFORE_2.0> sudo dnf versionlock add securecore

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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-2018-16160?

securecore: upgrade to 3.0. Exact commands for each OS are on this page.

Is CVE-2018-16160 being exploited?

CVE-2018-16160 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-2018-16160 affect?

CVE-2018-16160 affects securecore. Severity is high (CVSS 7.8). SecureCore Standard Edition Version 2.x allows an attacker to bypass the product 's authentication to log in to a Windows PC.

How urgent is CVE-2018-16160?

Priority 34/100. High severity

Software pages

Windows vulnerabilities

References

← Back to latest CVEs