Php To Page
Approved changes feed: RSS · Atom
cpe:2.3:a:bloafer:php_to_page:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Bloafer (a753b9fa-b4af-570b-b30b-2e0d77563ed1) |
|---|---|
| Product | Php To Page (b2dfdf2b-b851-5584-b833-411c8f30ca20) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-5199 |
vulnerable | 2026-06-08 06:19:42.864260 |
PHP to Page <= 0.3 - Authenticated (Subscriber+) Local File Inclusion to Remote Code Execution via Shortcode
CRITICAL (9.9)
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.
Published: 2023-10-30T13:48:58.665Z
Updated: 2026-04-08T17:04:16.035Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.