Skip to main content

Edge CPT CVE-2025-62868

HIGH
PHP Remote File Inclusion (CWE-98)
2025-10-24 audit@patchstack.com
8.1
CVSS 3.1 · Vendor: patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify site running Edge CPT ≤1.4
  2. Delivery
    Send request with crafted filename parameter
  3. Exploit
    Plugin includes attacker-controlled local path
  4. Execution
    Read sensitive files or include poisoned PHP
  5. Impact
    Disclose credentials or execute code on host

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V5 - File Handling File inclusion prevention, allowlisting
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Command and Control

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires a WordPress site running the Edge-Themes Edge CPT plugin at version 1.4 or earlier, reachable over the network. Per PR:N the base flaw needs no authentication, but the AC:H rating and CWE-98 nature mean reliable code execution (as opposed to file disclosure) depends on the attacker being able to control or poison an includable file on the host (e.g., log files, session files, or uploaded content) to be interpreted as PHP; pure file-read disclosure has the lowest barrier. No user interaction is required.

Impact

The vendor CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, 8.1 High) describes an unauthenticated, network-reachable PHP file-inclusion flaw with full CIA impact but elevated attack complexity (AC:H). The AC:H is credible for CWE-98 LFI: reading arbitrary local files is straightforward, but escalating to code execution (which the I:H/A:H impacts assume) requires an additional condition such as an attacker-poisonable file (log poisoning, session file, or uploaded content) to include as PHP - so the full-impact scoring is somewhat optimistic and the realistic worst case for a pure LFI is often high-confidentiality file disclosure. EPSS is 0.47% (38th percentile) - modest, consistent with a niche WordPress plugin. There is no CISA KEV listing and no public exploit code identified, so this is not confirmed to be under active exploitation. Net: a genuinely serious flaw class (unauthenticated LFI) but tempered by AC:H, low deployment footprint, and no exploitation signal - a patch-in-normal-cycle item rather than an emergency, unless the plugin is exposed on a high-value site. Note: the input tag 'Information Disclosure' understates the flaw, which per CVSS also carries integrity and availability impact.

Exploit ScenarioDerived

A remote unauthenticated attacker sends a crafted request to a vulnerable Edge CPT endpoint that passes attacker-influenced input into a PHP include/require, causing the plugin to include a local file. In the read-only case this leaks sensitive files (e.g., wp-config.php credentials); if the attacker can first plant PHP into an includable file (log/session/upload poisoning), the same inclusion yields remote code execution. No public proof-of-concept is currently identified, and the AC:H rating reflects the extra setup required for reliable code execution.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 30, 2026

Unauthenticated remote attackers can trigger a PHP file-inclusion condition in the WordPress plugin Edge CPT (Edge-Themes) at version 1.4 and earlier, allowing inclusion of attacker-influenced files and potentially leading to local file disclosure or, under the right conditions, PHP code execution. The vendor CVSS 3.1 vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, 8.1 High) rates confidentiality, integrity and availability impacts as full but assigns elevated attack complexity, because reliable code execution depends on the attacker being able to poison or control a file on the host that PHP will then parse; straightforward file-read disclosure has a much lower barrier. There is no indication of confirmed active exploitation and no public exploit code has been identified at time of analysis, and the EPSS score is low at 0.47% (38th percentile), suggesting limited near-term mass-exploitation pressure.

RemediationAI

No vendor-released patched version is identified in the available advisory data, so operators should not assume an upgrade path exists and should instead reduce exposure directly. The most effective compensating control is to deactivate and remove the Edge CPT plugin from any WordPress installation that does not strictly require it, accepting the loss of its custom-post-type functionality as the trade-off; where the plugin must remain, block unauthenticated access to its endpoints at the web server or WAF layer (for example by requiring authentication for requests reaching the plugin's PHP files) and restrict administrative access to the site. Harden the PHP environment to break the include chain: set allow_url_include=Off and allow_url_fopen=Off, apply open_basedir to confine file access to the WordPress document root, and confirm that upload, cache, log and session directories are not web-readable or executable as PHP, since those locations are the usual poisoning targets that raise this bug from file disclosure to code execution. Deploy WAF or server rules that reject traversal sequences and absolute-path parameters (../, php://filter, php://input, data://, and similar wrappers) in requests to the plugin, and enable file-integrity and access-log monitoring so that unexpected include attempts against wp-config.php or other sensitive files are detected and alerted. Monitor the Patchstack advisory and Edge-Themes release channels for a fixed version, and upgrade immediately once a patched release is published; as always, test any WordPress plugin removal or access restriction in staging first to confirm it does not break dependent custom post types or templates.

Affected ProductsAI

The affected product is the WordPress plugin Edge CPT published by Edge-Themes, covering all versions from the initial release (listed as n/a) through and including version 1.4. Any WordPress site with Edge CPT 1.4 or earlier installed and reachable over the network is in scope, regardless of which other Edge-Themes items are present. No CPE identifiers were provided in the supplied intelligence, and the sole reference is the Patchstack vulnerability database entry for the Edge CPT plugin 1.4 local file inclusion issue (https://patchstack.com/database/wordpress/plugin/edge-cpt/security-policy/vdp/vulnerability/wordpress-edge-cpt-plugin-1-4-local-file-inclusion-vulnerability?_s_id=cve), which should be treated as the authoritative source for the affected version range and any updated version guidance.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is classified as CWE-98, Improper Control of Filename for Include/Require Statement in PHP Program, commonly labeled PHP Remote/Local File Inclusion. In vulnerable WordPress plugins this class of bug typically arises when a user-controllable parameter is passed into PHP's include(), require(), include_once() or require_once() without an allowlist or path normalization, letting an attacker influence which file the interpreter loads. On the network-facing side the vector is AV:N with PR:N, meaning the request path requires no authentication, and UI:N means no victim interaction is needed; the AC:H rating reflects that successful exploitation to code execution requires the additional precondition of an attacker-controlled or attacker-poisoned includable file existing on the host (for example log files, session files, cache files, or uploaded content that can be coerced into PHP), whereas simple local file inclusion for reading sensitive files such as wp-config.php does not. The advisory identifies the product as the WordPress plugin Edge CPT, an Edge-Themes component; no CPE strings were supplied in the source data, so exact platform enumeration is limited to the plugin itself running on a WordPress installation. Tags associated with the issue (PHP, Information Disclosure, LFI) confirm that information disclosure via local file inclusion is the most directly reachable outcome.

Know when PHP gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (patchstack) PRIMARY 8.1 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.1 HIGH

Unauthenticated network LFI (PR:N/AV:N); AC:H because reaching full code-execution impact requires an attacker-poisonable include target; C:H from arbitrary file read, I:H/A:H accepted for the RCE case.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (patchstack).

CVSS VectorVendor: patchstack

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Edge-Themes Edge CPT allows PHP Local File Inclusion.This issue affects Edge CPT: from n/a through 1.4.

Executive ViewAI

Why It Matters

An unauthenticated flaw in the WordPress plugin Edge CPT (Edge-Themes), versions 1.4 and earlier, allows an external attacker to influence which files the web server loads, exposing sensitive server-side files and, in narrower circumstances, enabling code execution on the hosting platform. Any site running this plugin is potentially reachable by anyone on the internet without credentials, and because no vendor fix is currently available, the exposure persists until sites are remediated manually. Leadership should care because compromise of a public-facing WordPress host can lead to defacement, data exposure, and lateral movement into adjacent corporate systems, and the affected asset base and remediation effort must be sized now.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or remove the Edge CPT (Edge-Themes) plugin where it is not essential; virtual-patch at the WAF/reverse proxy by blocking traversal and file-inclusion patterns in plugin requests; disable allow_url_include and allow_url_fopen in PHP configuration; restrict the web server account with least privilege and open_basedir; make upload and writable directories non-executable and non-parseable to prevent file poisoning needed for code execution; enable file-integrity monitoring and alerting on include/require anomalies; segment the WordPress host from internal corporate networks.

Threat Intelligence Overview

EPSS Score
0.5%
Top 62% exploitable
Prevalence
Low
niche Edge-Themes WordPress custom-post-type plugin, limited install base
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.5%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

40
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +40
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Local File Inclusion vulnerabilities occur when an application accepts user-controlled input to specify which file should be loaded or executed, typically through functions like PHP's `include()`, `require()`, or `fopen()`.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

More in PHP

View all
CVE-2019-11043 CRITICAL POC
9.8 Oct 28

In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it

CVE-2012-1823 CRITICAL POC
9.8 May 11

sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not

CVE-2016-1555 CRITICAL POC
9.8 Apr 21

(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear

CVE-2018-11138 CRITICAL POC
9.8 May 31

The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by

CVE-2024-11680 CRITICAL POC
9.8 Nov 26

ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C

CVE-2025-49113 CRITICAL POC
9.9 Jun 02

Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au

CVE-2017-9841 CRITICAL POC
9.8 Jun 27

Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c

CVE-2025-0108 HIGH POC
8.8 Feb 12

Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers

CVE-2021-25298 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2021-25296 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2013-4983 CRITICAL POC
10.0 Sep 10

The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy