What is the CVSS score of CVE-2025-58994?

CVE-2025-58994 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 Greenify WordPress Theme are affected by CVE-2025-58994?

The Greenify WordPress theme (versions through 2.2) contains a local file inclusion vulnerability (CVSS 8.1) that could allow attackers to read sensitive files from affected web servers, including…

How to fix or mitigate CVE-2025-58994?

Within 24 hours: Identify all WordPress installations using Greenify theme versions 2.2 or earlier and take affected sites offline or disable the theme pending remediation. Within 7 days: Contact Greenify theme developers for patch availability and timeline; evaluate alternative themes or implement file access restrictions at the web server level. Within 30 days: Either upgrade to a patched version (if released) or migrate to an alternative supported WordPress theme; implement Web Application Firewall (WAF) rules to block suspicious file inclusion patterns as interim protection.

Greenify WordPress Theme CVE-2025-58994

HIGH

PHP Remote File Inclusion (CWE-98)

2025-11-06 audit@patchstack.com

LFI PHP Information Disclosure

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

Analysis Updated

Apr 24, 2026 - 00:42 vuln.today

v3 (cvss_changed)

Analysis Updated

Apr 24, 2026 - 00:42 vuln.today

v2 (cvss_changed)

Re-analysis Queued

Apr 23, 2026 - 15:43 vuln.today

cvss_changed

Analysis Generated

Mar 28, 2026 - 19:20 vuln.today

CVE Published

Nov 06, 2025 - 16:16 nvd

HIGH 8.1

DescriptionCVE.org

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in designervily Greenify greenify allows PHP Local File Inclusion.This issue affects Greenify: from n/a through <= 2.2.

AnalysisAI

Local file inclusion vulnerability in Greenify WordPress theme (versions through 2.2) enables remote attackers to read arbitrary files from the web server filesystem, potentially exposing sensitive configuration files, credentials, and application source code. Exploitation requires specific conditions despite the network attack vector, reflected in the high attack complexity (AC:H) rating. EPSS score of 0.08% (23rd percentile) suggests low probability of mass exploitation, and no active exploitation has been confirmed via CISA KEV, though Patchstack has documented the vulnerability details.

Technical ContextAI

This vulnerability stems from improper validation of file paths in PHP include/require statements (CWE-98). The Greenify WordPress theme fails to sanitize user-controlled input before passing it to file inclusion functions, allowing attackers to manipulate the file path parameter. While classified as 'PHP Remote File Inclusion' in the vulnerability type, the actual exploitation is Local File Inclusion (LFI), meaning attackers can read files already present on the server rather than inject remote code. This discrepancy between the vulnerability name and actual behavior is common in WordPress theme vulnerabilities where allow_url_include is typically disabled in modern PHP configurations. The affected product is a WordPress theme (not a plugin), which means the vulnerable code executes within the WordPress rendering context with web server privileges.

Affected ProductsAI

The vulnerability affects the Greenify WordPress theme developed by designervily, specifically all versions from the initial release through version 2.2. According to the CPE data and Patchstack advisory at https://patchstack.com/database/Wordpress/Theme/greenify/vulnerability/wordpress-greenify-theme-2-2-local-file-inclusion-vulnerability, version 2.2 is confirmed vulnerable. Organizations should verify their installed theme version through the WordPress admin panel under Appearance > Themes. The advisory does not specify a minimum affected version, suggesting all historical versions contain this flaw.

RemediationAI

Immediately upgrade to a patched version of the Greenify theme if available by checking the theme developer's website or WordPress theme repository for updates beyond version 2.2. Consult the Patchstack advisory at https://patchstack.com/database/Wordpress/Theme/greenify/vulnerability/wordpress-greenify-theme-2-2-local-file-inclusion-vulnerability for the latest remediation guidance. If no patched version exists, switch to an alternative WordPress theme from a reputable developer with active security maintenance. As an interim compensating control, implement Web Application Firewall (WAF) rules to block requests containing directory traversal sequences (../, ..\ , %2e%2e%2f) in URL parameters, though this may break legitimate theme functionality requiring file path parameters. Restrict file system permissions on sensitive configuration files like wp-config.php to prevent read access by the web server user where possible, though this may impact WordPress core functionality. Monitor web server access logs for suspicious requests containing encoded traversal attempts or references to sensitive filenames. These workarounds reduce but do not eliminate risk, so theme replacement remains the definitive solution.