# CVE-2024-8767: Privilege escalation in Acronis Backup extension for Plesk

> Attackers can escalate privileges to disclose and manipulate sensitive data in Acronis Backup plugins for cPanel, Plesk, and DirectAdmin.

- **Severity:** Critical 9.9 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2024
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-vmvq-4vv4-p8f9

## What is CVE-2024-8767?

CVE-2024-8767 is a critical vulnerability in Acronis Backup extension for Plesk, published on 17 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Sensitive data disclosure and manipulation due to unnecessary privileges assignment. The following products are affected: Acronis Backup plugin for cPanel & WHM (Linux) before build 619, Acronis Backup extension for Plesk (Linux) before build 555, Acronis Backup plugin for DirectAdmin (Linux) before build 147.

Weakness: CWE-250 (Execution with Unnecessary Privileges)

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


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

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

## Is CVE-2024-8767 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8767 is a critical vulnerability in Acronis Backup extension for Plesk, published on 17 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-8767 in the wild and no public exploit code.

Affected product: Acronis Backup extension for Plesk. 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-8767/ (Markdown: https://insights.sbomify.com/CVE-2024-8767/index.md)
```

## Sources

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

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