# CVE-2024-38770: Privilege escalation in Backup and Staging by WP Time Capsule

> Attackers can bypass authentication and escalate privileges in the WP Time Capsule plugin, compromising WordPress sites.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Aug 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-7hjj-wgf7-9885

## What is CVE-2024-38770?

CVE-2024-38770 is a critical vulnerability in Revmakx Backup and Staging by WP Time Capsule, published on 1 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Privilege Management vulnerability in Revmakx Backup and Staging by WP Time Capsule allows Privilege Escalation, Authentication Bypass.This issue affects Backup and Staging by WP Time Capsule: from n/a through 1.22.20.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2024-38770 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-38770 is a critical vulnerability in Revmakx Backup and Staging by WP Time Capsule, published on 1 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-38770 in the wild and no public exploit code.

Affected product: Revmakx Backup and Staging by WP Time Capsule. 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-38770/ (Markdown: https://insights.sbomify.com/CVE-2024-38770/index.md)
```

## Sources

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

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