Verdure Core EUVD-2026-65325

Two conditions must be satisfied for full RCE: the Verdure Core plugin must be installed and active at version 1.2 or earlier, and attacker-controlled file content must be present on the server filesystem - typically achieved via any upload endpoint accessible prior to authentication (e.g., media uploads, form attachments). The CVSS PR:N vector confirms no authentication is required to trigger the LFI itself. The AC:H rating explicitly signals elevated complexity, reflecting the file-staging prerequisite for RCE. Confidentiality impact (sensitive file disclosure via LFI without file staging) is achievable at lower complexity and represents a distinct, lower-bar exploitation path. Exploitation is bounded by the need for the plugin to be active and the AC:H constraint; sites that have disabled all guest-accessible upload endpoints reduce RCE risk but remain exposed to information disclosure. No specific non-default configuration flag or feature toggle is named in the description beyond plugin presence at a vulnerable version.

The CVSS 8.1 score (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) reflects unauthenticated network exploitation with elevated attack complexity and high impact across all three pillars. The AC:H metric is the critical moderating factor: successful RCE requires attacker-controlled file content to already reside on the server filesystem, introducing a chaining prerequisite that prevents trivial mass exploitation. Pure LFI for sensitive file disclosure (config files, credentials, logs) carries lower complexity and is a realistic threat even without a file-upload vector. No EPSS score was provided in the source intelligence, limiting probabilistic exploitation quantification. The absence of a CISA KEV entry and confirmed public exploit code keeps this in a moderate-to-high priority band rather than emergency response territory - but the unauthenticated network vector and full C/I/A impact mean any site running Verdure Core ≤ 1.2 with accessible upload endpoints should treat remediation as urgent. EPSS data missing from input; exploitation probability cannot be quantified from available signals.

An attacker targeting a WordPress site running Verdure Core ≤ 1.2 first identifies a publicly accessible file upload endpoint - such as a guest-allowed contact form, comment attachment feature, or open media endpoint - and uploads an image file containing an embedded PHP webshell. The attacker then sends a crafted HTTP request manipulating a path parameter in the Verdure Core plugin to reference the server-side path of the uploaded file, causing PHP to include and execute the embedded payload, granting the attacker a remote shell running as the web server user. No public exploit code has been identified at time of analysis, meaning this scenario currently requires manual, targeted effort rather than automated tooling.