CVE•Published 2023-10-30•Modified 2026-04-08•1 article on news•6 live references•NVD data

CVE-2023-5199Php_to_page_project · Php_to_page

Vulnerability data via NVD (ingested)

CVSS v3.1

9.9

CRITICAL

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

EPSS percentile

Exploit Prediction Scoring System · top 10% of all CVEs

Weaknesses (CWE)

CWE-98Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')CWE-552Files or Directories Accessible to External Parties

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.

Timeline

Published 2023-10-30

Modified 2026-04-08

External references

NVD MITRE Exploit-DB GitHub PoC trickest/cve VulnCheck

Search for exposed instances

Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common).

Shodan · vuln tag0 hosts

vuln:CVE-2023-5199

Hosts Shodan has explicitly fingerprinted as vulnerable.

Shodan · WP plugin path

http.html:"/wp-content/plugins/php-to-page/"

Matches any site loading the "php-to-page" plugin — doesn't rely on Shodan's vuln tag.

Shodan · product

product:"Php To Page Project Php To Page"

All exposed Php To Page Project Php To Page instances — cross-reference with the CVE's affected-version range.

Shodan · banner/body mention

http.html:"Php To Page"

HTTP body or banner mentions "Php To Page" — catches deploys Shodan didn't identify as a product.