dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-4824

HIGH · 7.0 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been found in Enter Software Iperius Backup up to 8.7.3. Affected by this issue is some unknown functionality of the component Backup Job Configuration File Handler. The manipulation leads to improper privilege management. The attack must be carried out locally. The attack is considered to have high complexity. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. Upgrading to version 8.7.4 can resolve this issue. It is advisable 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A privilege management vulnerability exists in Iperius Backup's Backup Job Configuration File Handler (versions up to 8.7.3). The flaw allows local attackers to manipulate backup job configurations due to improper privilege handling, potentially elevating their privileges or altering backup behavior.

MitigationUpgrade Iperius Backup to version 8.7.4 to resolve the improper privilege management in the configuration file handler.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Iperius Backup installation
    Check for Iperius Backup installation by looking in common program directories: C:\Program Files\Iperius Backup or C:\Program Files (x86)\Iperius Backup, or search for iperius.exe in the system
    Affected if Iperius Backup is found on the system
  2. Determine installed version
    Right-click on the Iperius Backup executable (iperius.exe), select Properties, and check the Details tab for the Product Version, or launch Iperius Backup and look for the version number in the About or Help section
    Affected if Version cannot be determined or is 8.7.3 or lower
  3. Compare version against affected range
    Compare the installed version number to the affected range (all versions up to and including 8.7.3). Note that version 8.7.4 is the fixed release.
    Affected if Installed version is 8.7.3 or any earlier version (e.g., 8.7.2, 8.7.1, 8.7.0, etc.)
  4. Identify backup job configuration files
    Locate Iperius Backup job configuration files, typically stored in the application data folder (e.g., %APPDATA%\Iperius Backup\ or in the installation directory under a Jobs or Backups subfolder). These are commonly .ibj or .xml files.
    Affected if Configuration files exist and the application handles them with improper privilege management in affected versions

The environment is affected if Iperius Backup is installed and the installed version is 8.7.3 or any earlier version, since the privilege management vulnerability exists in all versions up to 8.7.3 in the Backup Job Configuration File Handler.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Iperius Backup to version 8.7.4 to resolve the improper privilege management in the configuration file handler.

Recommended fix High confidence

8.7.4

  1. Download Iperius Backup version 8.7.4 from the official vendor website (www.iperiusbackup.com)
  2. Ensure all backup jobs are stopped or completed before upgrading
  3. Install version 8.7.4 over the existing installation
  4. Verify the upgrade was successful by checking the installed version in the application
  5. Test that backup jobs function correctly after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4824 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4824 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data