What is the CVSS score of CVE-2026-27093?

CVE-2026-27093 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 CVE-2026-27093?

The Ovatheme Tripgo WordPress theme versions below 1.5.6 contain a remote file inclusion vulnerability that permits unauthenticated attackers to execute arbitrary code and access sensitive…. A patch is available.

How to fix or mitigate CVE-2026-27093?

Within 24 hours: identify all WordPress sites using Ovatheme Tripgo theme and document current version numbers. Within 7 days: upgrade all affected installations to version 1.5.6 or later, and validate successful updates across all environments. Within 30 days: conduct security audit of affected sites for evidence of exploitation, review access logs for suspicious file inclusion attempts, and implement Web Application Firewall rules to block file inclusion patterns if immediate patching is not possible.

PHP CVE-2026-27093

EUVD-2026-13068 HIGH

PHP Remote File Inclusion (CWE-98)

2026-03-19 Patchstack

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 23, 2026 - 16:12 vuln.today

cvss_changed

Analysis Updated

Apr 16, 2026 - 06:20 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.5.6

EUVD ID Assigned

Mar 19, 2026 - 07:15 euvd

EUVD-2026-13068

Analysis Generated

Mar 19, 2026 - 07:15 vuln.today

CVE Published

Mar 19, 2026 - 06:41 nvd

HIGH 8.1

DescriptionCVE.org

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Ovatheme Tripgo allows PHP Local File Inclusion.This issue affects Tripgo: from n/a before 1.5.6.

AnalysisAI

A PHP remote/local file inclusion vulnerability exists in the Ovatheme Tripgo WordPress theme due to improper control of filename parameters in include/require statements. Versions prior to 1.5.6 are affected, allowing unauthenticated remote attackers to potentially include arbitrary files and execute malicious code. This vulnerability has a CVSS score of 8.1 (High) with network attack vector but high attack complexity, and has been reported by Patchstack as exploitable for local file inclusion and information disclosure.

Technical ContextAI

This vulnerability is classified under CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program), commonly known as PHP file inclusion. The affected product is Ovatheme Tripgo (CPE: cpe:2.3:a:ovatheme:tripgo:*:*:*:*:*:*:*:*), a WordPress theme written in PHP. The flaw arises when user-controlled input is used to construct file paths passed to PHP's include() or require() functions without proper validation or sanitization. While the CVE description mentions remote file inclusion, Patchstack has tagged this specifically as Local File Inclusion (LFI), suggesting the vulnerability allows attackers to read arbitrary files from the server's filesystem rather than including remote resources, though the distinction may depend on PHP configuration settings like allow_url_include.

RemediationAI

Upgrade the Ovatheme Tripgo WordPress theme to version 1.5.6 or later, which addresses the file inclusion vulnerability according to the version range specified in the CVE. The patch details and download are available through Ovatheme's official distribution channels and referenced in the Patchstack advisory at https://patchstack.com/database/wordpress/theme/tripgo/vulnerability/wordpress-tripgo-theme-1-5-3-local-file-inclusion-vulnerability. Until upgrading is possible, implement defense-in-depth measures including restricting file system permissions to prevent web server access to sensitive files outside the web root, disabling PHP functions like allow_url_include in php.ini if enabled, deploying web application firewall rules to detect and block path traversal attempts, and monitoring server logs for suspicious include/require patterns. Consider temporarily switching to a different theme if immediate patching cannot be performed.