# CVE-2023-0958: Inisev Plugins (Various Versions) - Missing Authorization on handle_installation function

> Authenticated attackers with minimal permissions can install specific Inisev plugins due to missing authorization checks, potentially leading to privilege escalation or code execution.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **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:** 28 Jul 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-hpq9-m2jp-4fgr

## What is CVE-2023-0958?

CVE-2023-0958 is a medium-severity missing authorization vulnerability in cl272 BackupBliss – Backup & Migration with Free Cloud Storage, published on 28 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Several plugins for WordPress by Inisev are vulnerable to unauthorized installation of plugins due to a missing capability check on the handle_installation function that is called via the inisev_installation AJAX aciton in various versions. This makes it possible for authenticated attackers with minimal permissions, such as subscribers, to install select plugins from Inisev on vulnerable sites. CVE-2023-38514 appears to be a duplicate of this vulnerability.

Weakness: CWE-862 (Missing Authorization)

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

It affects 11 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, Socialshare Social Share Icons \& Social Share Buttons, Ultimatelysocial Social Media Share Buttons \& Social Sharing Icons.

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

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

## Is CVE-2023-0958 being exploited?

There is no known exploitation of CVE-2023-0958 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-0958 and fix it if it is affected.

What it is: CVE-2023-0958 is a medium-severity missing authorization vulnerability in cl272 BackupBliss – Backup & Migration with Free Cloud Storage, published on 28 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-0958 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-0958/ (Markdown: https://insights.sbomify.com/CVE-2023-0958/index.md)
```

## Sources

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

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