CVE-2026-5310VulnerabilityPublished 1 Apr 2026

CVE-2026-5310: Enter Software Iperius Backup · Use of Hard-coded Cryptographic Key

Affects Enter Software Iperius BackupSource CVE Database V5

Not known to be exploited · CVSS 2.0 Low.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score

2.0Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.09% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Local
Attack Complexity: High
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Enter SoftwareIperius Backup	Affected =8.7.0 =8.7.1 =8.7.2	Fixed in–
GitHubvulnarabyte/iperius-backup-security-advisories`pkg:github/vulnarabyte/iperius-backup-security-advisories`Other threats	Affected =8.7.0 =8.7.1 =8.7.2	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-5310, organizations should immediately upgrade Iperius Backup to version 8.7.4 or later, which contains the fix for the hard-coded cryptographic key vulnerability. Additionally, restrict local access to systems running Iperius Backup to trusted administrators only, minimizing the risk of exploitation by unauthorized users. Implement strict access controls and monitoring on backup servers to detect any unusual local activity. Review and rotate any cryptographic keys or credentials that may have been exposed due to this vulnerability. Conduct regular audits of backup configurations and files, including IperiusAccounts.ini, to detect unauthorized changes. Employ endpoint protection and host-based intrusion detection systems to identify attempts to exploit local vulnerabilities. Educate system administrators about the risks of hard-coded keys and encourage secure key management practices. Finally, maintain an up-to-date inventory of software versions in use to ensure timely patching of vulnerabilities.

Description

A vulnerability was identified in Enter Software Iperius Backup up to 8.7.2. This impacts an unknown function of the file IperiusAccounts.ini. Such manipulation leads to use of hard-coded cryptographic key . The attack must be carried out locally. This attack is characterized by high complexity. The exploitability is said to be difficult. The exploit is publicly available and might be used. Upgrading to version 8.7.4 will fix this issue. It is suggested to upgrade the affected component. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.

Impact

The primary impact of CVE-2026-5310 is the potential compromise of cryptographic protections within Iperius Backup due to the use of a hard-coded key. If exploited, an attacker with local access could potentially decrypt or manipulate backup data or bypass authentication mechanisms, undermining data confidentiality and integrity. However, the requirement for local access and the high complexity of exploitation limit the scope and likelihood of attacks. The vulnerability does not directly affect system availability. Organizations relying on Iperius Backup for critical data protection could face increased risk of data exposure or tampering if the vulnerability is exploited. This could lead to data loss, regulatory compliance issues, and erosion of trust in backup integrity. Since the exploit is publicly available, the risk of opportunistic attacks exists, especially in environments with weak internal security controls. The impact is more pronounced in environments where multiple users have local access or where attackers have already gained foothold through other means. Overall, the threat is low but non-negligible, particularly for organizations with sensitive data and stringent security requirements.

Summary

CVE-2026-5310 identifies a security vulnerability in Enter Software's Iperius Backup product, specifically in versions 8.7.0 through 8.7.2. The issue arises from the use of a hard-coded cryptographic key within the IperiusAccounts.ini configuration file. Hard-coded keys are a critical security weakness because they can be extracted by an attacker who gains access to the system, potentially allowing unauthorized decryption or manipulation of backup data or authentication mechanisms. Exploiting this vulnerability requires local access to the affected system and low-level privileges, making remote exploitation infeasible. The attack complexity is high, indicating that a skilled attacker with detailed knowledge and access is needed to exploit the flaw effectively. The vulnerability does not require user interaction and does not affect confidentiality, integrity, or availability on a large scale, reflected in its low CVSS score of 2.0. The vendor responded quickly and professionally by releasing version 8.7.4, which addresses the issue by removing or replacing the hard-coded key. Although a public exploit exists, there are no reports of active exploitation in the wild, reducing immediate risk. However, the presence of a public exploit means that organizations should prioritize patching to prevent potential misuse. The vulnerability affects an unknown function related to the IperiusAccounts.ini file, which likely handles authentication or encryption keys for backup operations, making it a sensitive component for data protection.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 1 Apr 2026, 18:24 UTC

Technical details

References

Community reviews

Related threats