# CVE-2024-7562: Privilege escalation in InstallShield

> Attackers can escalate privileges when using InstallShield standalone MSI setups with multiple InstallScript custom actions.

- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2025
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-6mwp-44r4-pwrq

## What is CVE-2024-7562?

CVE-2024-7562 is a high-severity vulnerability in Revenera InstallShield, published on 12 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A potential elevated privilege issue has been reported with InstallShield built Standalone MSI setups having multiple InstallScript custom actions configured. All supported versions (InstallShield 2023 R2, InstallShield 2022 R2 and InstallShield 2021 R2) are affected by this issue.

Weakness: CWE-379 (Creation of Temporary File in Directory with Insecure Permissions)

## Which versions are affected by CVE-2024-7562?


## How do I fix CVE-2024-7562?

No fix has been published for CVE-2024-7562 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-7562 being exploited?

There is no known exploitation of CVE-2024-7562 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-7562 and fix it if it is affected.

What it is: CVE-2024-7562 is a high-severity vulnerability in Revenera InstallShield, published on 12 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-7562 in the wild and no public exploit code.

Affected product: Revenera InstallShield. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-7562/ (Markdown: https://insights.sbomify.com/CVE-2024-7562/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-7562
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-7562
- OSV: https://osv.dev/vulnerability/CVE-2024-7562

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-7562/
Summaries are generated and may contain mistakes; the official description above is the record.