CVE
Privilege escalation in Enter’s Iperius Backup
Only affects Iperius Backup 8.8.3 for Windows when the backup service is configured to run persistently with Administrator privileges. Fixed in 8.8.9.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- Public exploit code, no confirmed attacks
- Fix
- Fixed in 8.8.9
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Iperius Backup version 8.8.3 for Windows Backup service configured to run persistently with Administrator privileges
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- First public exploit on GitHub Nov 11
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 36/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
Summary
Enter's Iperius Backup has a local privilege escalation flaw: a low-privileged user on the same Windows machine can abuse the application's native dialogues to run programs that inherit its elevated context. This requires the backup service to be configured to run persistently with Administrator privileges, and it can lead to commands running as SYSTEM or Administrator, fully compromising the system.
Read the original description
Local privilege escalation vulnerability in Iperius Backup 8.8.3, due to insufficient separation between the graphical user interface running with elevated privileges and local users with low privileges. When the backup service is configured to run persistently with Administrator privileges, a local attacker with low privileges can use the native Windows dialogues exposed by the application to run programmes that inherit its elevated context. This allows commands to be executed with SYSTEM or Administrator privileges, depending on the application’s context, and compromises the affected Windows system.
Who should check
Teams running Iperius Backup 8.8.3 for Windows where the backup service runs persistently with Administrator privileges.
cve.now Index
- Exploitation22/40Public exploit on Exploit-DB or GitHub · Unknown: No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 46 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Iperius Backup version 8.8.3 for Windows Backup service configured to run persistently with Administrator privilegesUpgrade to a fixed version: 8.8.9.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-112174 (Privilege escalation in Enter’s Iperius Backup), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-112174 (entry last updated 2026-11-11):
Affected:
- Enter Iperius Backup: versions 8.8.3 for Windows
Fixed versions: 8.8.9.
Conditions (all must be true for the bug to be hit):
- Iperius Backup version 8.8.3 for Windows (source: https://www.incibe.es/en/incibe-cert/notices/aviso/privilege-escalation-enters-iperius-backup)
- Backup service configured to run persistently with Administrator privileges (source: https://www.incibe.es/en/incibe-cert/notices/aviso/privilege-escalation-enters-iperius-backup)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
CISA KEV: CVE-2026-112174 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-112174 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.incibe.es/en/incibe-cert/notices/aviso/privilege-escalation-enters-iperius-backup
- https://www.cve.org/CVERecord?id=CVE-2026-112174
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-112174
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-112174"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- Exploit code on GitHub
jonastrikex/CVE-2026-112174-Iperius-Backup-version-8.8.3-PoC
Affected versions
- Enter Iperius Backup
8.8.3 for Windows
Evidence 4
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Public exploit code · 1
Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-112174
Is CVE-2026-112174 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).Source: cve.now feed data
What does this mean?
The flaw allows commands to be executed with SYSTEM or Administrator privileges, which compromises the affected Windows system.Source: incibe.es, cve.org
Which versions are affected by CVE-2026-112174?
Iperius Backup: version 8.8.3 for Windows.Source: cve.now feed data
Am I affected, and how do I check?
The issue involves Iperius Backup version 8.8.3 for Windows, when the backup service is configured to run persistently with Administrator privileges. To check, look at the installed Iperius Backup version and at how the backup service is configured to run.Source: incibe.es, cve.org