# CVE-2024-27191: WordPress Slivery Extender plugin <= 1.0.2 - Remote Code Execution (RCE) vulnerability

> Attackers can execute arbitrary code via remote code inclusion in the Slivery Extender WordPress plugin.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:H/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:** 3 Apr 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-2g7p-7mvp-pw7m

## What is CVE-2024-27191?

CVE-2024-27191 is a high-severity code injection vulnerability in inpersttion Slivery Extender, published on 3 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Control of Generation of Code ('Code Injection') vulnerability in inpersttion Slivery Extender slivery-extender allows Remote Code Inclusion.This issue affects Slivery Extender: from n/a through <= 1.0.2.

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

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


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

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

## Is CVE-2024-27191 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-27191 is a high-severity code injection vulnerability in inpersttion Slivery Extender, published on 3 Apr 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-27191 in the wild and no public exploit code.

Affected product: inpersttion Slivery Extender. 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-27191/ (Markdown: https://insights.sbomify.com/CVE-2024-27191/index.md)
```

## Sources

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

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