# CVE-2023-5199: PHP to Page <= 0.3 - Authenticated (Subscriber+) Local File Inclusion to Remote Code Execution via Shortcode

> Authenticated attackers can achieve remote code execution via local file inclusion in the PHP to Page WordPress plugin.

- **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 Oct 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-pwfp-gqpx-2mgg

## What is CVE-2023-5199?

CVE-2023-5199 is a critical vulnerability in bloafer PHP to Page, published on 30 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The PHP to Page plugin for WordPress is vulnerable Local File Inclusion to Remote Code Execution in versions up to, and including, 0.3 via the 'php-to-page' shortcode. This allows authenticated attackers with subscriber-level permissions or above, to include local file and potentially execute code on the server. While subscribers may need to poison log files or otherwise get a file installed in order to achieve remote code execution, author and above users can upload files by default and achieve remote code execution easily.

Weakness: CWE-552 (Files or Directories Accessible to External Parties), CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

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

It affects 1 product.


Products: Php to Page Project Php to Page.

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

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

## Is CVE-2023-5199 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-5199 is a critical vulnerability in bloafer PHP to Page, published on 30 Oct 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-5199 in the wild and no public exploit code.

Affected product: bloafer PHP to Page. 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-5199/ (Markdown: https://insights.sbomify.com/CVE-2023-5199/index.md)
```

## Sources

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

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