CVE-2017-7312: An issue was discovered in Personify360 e-Business 7.5.2 through 7.6.1

This week

CRITICAL 9.8REMOTEDOWNGRADE

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

An issue was discovered in Personify360 e-Business 7.5.2 through 7.6.1. When going to the /TabId/275 URI, anyone can add a vendor account or read existing vendor account data (including usernames and passwords).

Why this priority

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

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	3.0% (top 13%)
CISA exploited list	No
Weakness	CWE-269
Published	2017-06-07
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: personifycorp

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

Am I affected?

Timeline

2017-06-07 13:29 UTCPublished CVE record published
2026-06-17 01:24 UTCUpdated Record last modified

personifycorp personify360 DOWNGRADE

Affected: 7.5.2 · 7.6 · 7.6.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 7.5.2

1. Check installed version

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

2. No fixed release: DOWNGRADE to a release before 7.5.2 (Debian / Ubuntu)

apt-cache madison personify360 sudo apt install personify360=<VERSION_BEFORE_7.5.2> sudo apt-mark hold personify360

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list personify360 sudo dnf downgrade personify360-<VERSION_BEFORE_7.5.2> sudo dnf versionlock add personify360

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.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: Personify360 7.5.2/7.6.1 - Improper Access Restrictions

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-2017-7312?

personify360: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-7312 being exploited?

CVE-2017-7312 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-2017-7312 affect?

CVE-2017-7312 affects personify360. Severity is critical (CVSS 9.8). An issue was discovered in Personify360 e-Business 7.5.2 through 7.6.1. When going to the /TabId/275 URI, anyone can add a vendor account or read existing vendor account data (including usernames and passwords).

How urgent is CVE-2017-7312?

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

References

← Back to latest CVEs