# CVE-2023-6553: Backup Migration <= 1.3.7 - Unauthenticated Remote Code Execution

> Unauthenticated attackers can execute arbitrary code on the server via the Backup Migration WordPress plugin.

- **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:** 15 Dec 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-2rcj-3wpj-27f2

## What is CVE-2023-6553?

CVE-2023-6553 is a critical code injection vulnerability in inisev BackupBliss – Backup & Migration with Free Cloud Storage, published on 15 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.3.7 via the /includes/backup-heart.php file. This is due to an attacker being able to control the values passed to an include, and subsequently leverage that to achieve remote code execution. This makes it possible for unauthenticated attackers to easily execute code on the server.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2023-6553?

It affects 1 product.


Products: Backupbliss Backup Migration.

## How do I fix CVE-2023-6553?

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

## Is CVE-2023-6553 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-6553 exists.

Public exploit code:

- Backup Migration <= 1.3.7 - Unauthenticated Remote Code Execution (github_poc): https://github.com/Chocapikk/CVE-2023-6553
- https://github.com/motikan2010/CVE-2023-6553-PoC (github_poc): https://github.com/motikan2010/CVE-2023-6553-PoC
- The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.3.7 via the /includes/backup-heart.php file. (github_poc): https://github.com/0x00phantom-hat/CVE-2023-6553-RCE-Exploit
- WordPress Backup Migration Plugin PHP Filter Chain RCE (metasploit)
- CVE-2023-6553 exploit script (github_poc): https://github.com/cc3305/CVE-2023-6553
- Exploit Development for CVE-2023-6553 on Backup Plugin in Wordpress (github_poc): https://github.com/Harshit-Mashru/CVE-2023-6553

## Other vulnerabilities in inisev BackupBliss – Backup & Migration with Free Cloud Storage

- [CVE-2023-6972](https://insights.sbomify.com/CVE-2023-6972/): Backup Migration <= 1.3.9 - Unauthenticated Path Traversal to Arbitrary File Deletion (critical 9.8)
- [CVE-2023-6971](https://insights.sbomify.com/CVE-2023-6971/): Code injection in Backup Migration (high 8.1)
- [CVE-2023-6266](https://insights.sbomify.com/CVE-2023-6266/): Backup Migration <= 1.3.6 - Unauthenticated Arbitrary Backup Download to Sensitive Information Exposure (high 7.5)
- [CVE-2023-6271](https://insights.sbomify.com/CVE-2023-6271/): Backup Migration Staging < 1.3.6 - Sensitive Data Exposure (high 7.5)
- [CVE-2023-7002](https://insights.sbomify.com/CVE-2023-7002/): Backup Migration <= 1.3.9 - Authenticated (Admin+) OS Command Injection via url (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6553 and fix it if it is affected.

What it is: CVE-2023-6553 is a critical code injection vulnerability in inisev BackupBliss – Backup & Migration with Free Cloud Storage, published on 15 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-6553 exists.

Affected product: inisev BackupBliss – Backup & Migration with Free Cloud Storage. 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-2023-6553/ (Markdown: https://insights.sbomify.com/CVE-2023-6553/index.md)
```

## Sources

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

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