# CVE-2023-5201: OpenHook <= 4.3.0 - Authenticated (Subscriber+) Remote Code Execution via Shortcode

> Authenticated attackers can execute arbitrary code on the server via the PHP shortcode if enabled.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/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:** 30 Sep 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-52wg-h24c-3wgr

## What is CVE-2023-5201?

CVE-2023-5201 is a critical code injection vulnerability in brazenlygeek OpenHook, published on 30 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The OpenHook plugin for WordPress is vulnerable to Remote Code Execution in versions up to, and including, 4.3.0 via the 'php' shortcode. This allows authenticated attackers with subscriber-level permissions or above, to execute code on the server. This requires the [php] shortcode setting to be enabled on the vulnerable site.

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

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

It affects 1 product.


Products: Rickbeckman Openhook.

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

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

## Is CVE-2023-5201 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-5201 is a critical code injection vulnerability in brazenlygeek OpenHook, published on 30 Sep 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-5201 in the wild and no public exploit code.

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

## Sources

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

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