# CVE-2026-27436: WordPress Five Star Business Profile and Schema plugin <= 2.3.19 - Arbitrary Code Execution vulnerability

> An editor can execute arbitrary code in the Five Star Business Profile and Schema WordPress plugin, potentially compromising the site.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jul 2026
- **Updated:** 2 Jul 2026
- **Also known as:** GHSA-5qwh-74pw-p44j

## What is CVE-2026-27436?

CVE-2026-27436 is a critical code injection vulnerability in Rustaurius Five Star Business Profile and Schema, published on 2 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Editor Arbitrary Code Execution in Five Star Business Profile and Schema <= 2.3.19 versions.

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

## Which versions are affected by CVE-2026-27436?


## How do I fix CVE-2026-27436?

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

## Is CVE-2026-27436 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-27436 and fix it if it is affected.

What it is: CVE-2026-27436 is a critical code injection vulnerability in Rustaurius Five Star Business Profile and Schema, published on 2 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-27436 in the wild and no public exploit code.

Affected product: Rustaurius Five Star Business Profile and Schema. 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-2026-27436/ (Markdown: https://insights.sbomify.com/CVE-2026-27436/index.md)
```

## Sources

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

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