What is the CVSS score of EUVD-2026-15901?

EUVD-2026-15901 has a CVSS 3.1 base score of 8.1 (High). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

Which versions of PHP are affected by EUVD-2026-15901?

Gavias Kunco WordPress theme versions before 1.4.5 contain a local file inclusion vulnerability (CVSS 8.1) that allows unauthenticated attackers to read arbitrary files from affected servers,…. A patch is available.

How to fix or mitigate EUVD-2026-15901?

Within 24 hours: Identify all WordPress installations using Gavias Kunco theme and document current versions. Within 7 days: Update Gavias Kunco theme to version 1.4.5 or later on all affected WordPress sites; verify successful update completion. Within 30 days: Conduct file access logs audit for the past 90 days to detect potential exploitation; review and rotate any credentials exposed in configuration files.

PHP EUVD-2026-15901

| CVE-2026-32531 HIGH

PHP Remote File Inclusion (CWE-98)

2026-03-25 Patchstack

GHSA-mhr3-454m-4wv6

PHP Information Disclosure LFI

8.1

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.1 HIGH

AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Re-analysis Queued

Apr 24, 2026 - 16:37 vuln.today

cvss_changed

Analysis Updated

Apr 16, 2026 - 06:14 EUVD-patch-fix

executive_summary

Re-analysis Queued

Apr 16, 2026 - 05:29 backfill_euvd_patch

patch_released

Patch available

Apr 16, 2026 - 05:29 EUVD

1.4.5

EUVD ID Assigned

Mar 25, 2026 - 16:47 euvd

EUVD-2026-15901

Analysis Generated

Mar 25, 2026 - 16:47 vuln.today

CVE Published

Mar 25, 2026 - 16:15 nvd

HIGH 8.1

DescriptionCVE.org

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in gavias Kunco kunco allows PHP Local File Inclusion.This issue affects Kunco: from n/a through < 1.4.5.

AnalysisAI

A Local File Inclusion (LFI) vulnerability exists in Gavias Kunco WordPress theme versions prior to 1.4.5, allowing attackers to read arbitrary files from the affected server through improper control of filename parameters in PHP include/require statements. This vulnerability enables information disclosure attacks where sensitive files such as configuration files, source code, or system files could be exposed to unauthenticated or low-privileged attackers. No CVSS score or EPSS data is currently available, but the vulnerability is classified under CWE-98 (Improper Control of Filename for Include/Require Statement), a critical class of PHP-based remote/local file inclusion flaws.

Technical ContextAI

The vulnerability is rooted in CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program), which describes unsafe handling of user-controlled input passed to PHP functions like include(), require(), include_once(), or require_once(). In the context of the Gavias Kunco WordPress theme (identified via CPE cpe:2.3:a:gavias:kunco:*:*:*:*:*:*:*:*), the code fails to properly validate or sanitize filename parameters before using them in include/require statements. This allows an attacker to manipulate the file path to include arbitrary files from the server's filesystem (Local File Inclusion) or, in some cases, remote servers (Remote File Inclusion). WordPress themes run with the privileges of the WordPress application, giving attackers access to read files within the web root and potentially outside it if the application has sufficient filesystem permissions.

RemediationAI

Upgrade Gavias Kunco theme to version 1.4.5 or later immediately. Site administrators should access the WordPress dashboard, navigate to Appearance > Themes, and update Kunco to the patched version available through WordPress.org or the vendor's update mechanism. Until patching is completed, apply temporary mitigations: restrict access to the WordPress admin panel via IP whitelisting, disable direct file access in wp-config.php by ensuring ABSPATH and other paths are not user-controllable, and implement Web Application Firewall rules to detect and block LFI payloads (common patterns include directory traversal sequences like ../ and file paths like /etc/passwd). Monitor access logs for suspicious file inclusion attempts. Verify after patching by reviewing the Patchstack advisory for confirmation of the fix.