cve.bz

CVE-2023-5199 php to page project php to page: Remote file include

8.8 highExploit referenceEPSS 1.7%

High (8.8) in php to page project php to page. EPSS 1.7% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
1.7% (unchanged from 1.7% a week ago; 1.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 78th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2025-02-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program (Remote file include)
CWE-552 Files or Directories Accessible to External Parties
OWASP Top 10
A01:2025 Broken Access Control, A05:2025 Injection
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2023-5199 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-5199?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-5199?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-5199 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
bloafer PHP to Pagethrough 0.3

Attack patterns (CAPEC)

  • CAPEC-193 PHP Remote File Inclusion Likelihood: High · Severity: High
  • CAPEC-150 Collect Data from Common Resource Locations Severity: Medium
  • CAPEC-639 Probe System Files Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON