# CVE-2023-3977: Inisev Plugins (Various Versions) - Cross-Site Request Forgery on handle_installation function

> Unauthenticated attackers can force site administrators to install plugins via CSRF, potentially leading to privilege escalation or code execution.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Jul 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-6jhg-gg85-9xxf

## What is CVE-2023-3977?

CVE-2023-3977 is a medium-severity vulnerability in cl272 BackupBliss – Backup & Migration with Free Cloud Storage, published on 28 Jul 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Several plugins for WordPress by Inisev are vulnerable to Cross-Site Request Forgery to unauthorized installation of plugins due to a missing nonce check on the handle_installation function that is called via the inisev_installation AJAX aciton in various versions. This makes it possible for unauthenticated attackers to install plugins from the limited list via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 10 products.


Products: Backupbliss Backup Migration, Backupbliss Clone, Copy-Delete-Posts Duplicate Post, Inisev Enhanced Text Widget, Inisev Redirection, Inisev Rss Redirect \& Feedburner Alternative, Inisev Ssl Mixed Content Fix, Inisev Ultimate Posts Widget, Mypopups Pop-Up, Ultimatelysocial Social Media Share Buttons \& Social Sharing Icons.

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

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

## Is CVE-2023-3977 being exploited?

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

## Other vulnerabilities in cl272 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-6553](https://insights.sbomify.com/CVE-2023-6553/): Backup Migration <= 1.3.7 - Unauthenticated Remote Code Execution (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)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-3977 is a medium-severity vulnerability in cl272 BackupBliss – Backup & Migration with Free Cloud Storage, published on 28 Jul 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-3977 in the wild and no public exploit code.

Affected product: cl272 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-3977/ (Markdown: https://insights.sbomify.com/CVE-2023-3977/index.md)
```

## Sources

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

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