Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-28064: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in ThemeREX Edge Decor

0
Unknown
VulnerabilityCVE-2026-28064cvecve-2026-28064
Published: Thu Mar 05 2026 (03/05/2026, 05:54:19 UTC)
Source: CVE Database V5
Vendor/Project: ThemeREX
Product: Edge Decor

Description

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in ThemeREX Edge Decor edge-decor allows PHP Local File Inclusion.This issue affects Edge Decor: from n/a through <= 2.2.

AI-Powered Analysis

AILast updated: 03/05/2026, 07:06:54 UTC

Technical Analysis

CVE-2026-28064 identifies a Local File Inclusion (LFI) vulnerability in the ThemeREX Edge Decor WordPress theme, specifically due to improper control over the filename parameter used in PHP include or require statements. This vulnerability arises when user-supplied input is not properly sanitized or validated before being passed to PHP functions that include files, allowing attackers to specify arbitrary files on the server to be included and executed within the application context. The affected product is Edge Decor versions up to 2.2. LFI vulnerabilities can be exploited to read sensitive files such as configuration files, password stores, or logs, and in some cases, combined with other vulnerabilities, can lead to remote code execution. Although no public exploits are currently documented, the flaw's presence in a widely used WordPress theme poses a significant risk. The vulnerability was reserved and published in early 2026, but no CVSS score has been assigned yet. The lack of patch links suggests that a fix may not yet be available or publicly disclosed. The vulnerability's exploitation complexity depends on how the theme processes input controlling the include path and whether authentication or specific user roles are required to trigger the flaw.

Potential Impact

The impact of this vulnerability is substantial for organizations using the Edge Decor theme on WordPress sites. Successful exploitation can lead to unauthorized disclosure of sensitive server files, including credentials, configuration data, and application source code, compromising confidentiality. Attackers might also execute arbitrary code if they can include files containing malicious payloads, threatening integrity and availability. This can result in website defacement, data breaches, or full server compromise. For businesses relying on WordPress for e-commerce, customer portals, or content management, such breaches can cause reputational damage, regulatory penalties, and financial losses. The scope is limited to sites using the vulnerable theme versions, but given WordPress's global popularity, the number of affected sites could be significant. The absence of known exploits in the wild currently reduces immediate risk, but the vulnerability remains a critical attack vector if weaponized.

Mitigation Recommendations

Organizations should immediately audit their WordPress installations to identify the use of the Edge Decor theme and verify the version. If running version 2.2 or earlier, they should seek updates or patches from ThemeREX as soon as they become available. In the absence of official patches, applying virtual patching via Web Application Firewalls (WAFs) to block suspicious requests attempting to manipulate include paths is recommended. Restricting file permissions on the server to limit access to sensitive files can reduce exploitation impact. Additionally, disabling PHP functions like include(), require(), or configuring open_basedir restrictions can mitigate LFI risks. Regularly monitoring web server logs for anomalous requests targeting file inclusion parameters can help detect exploitation attempts early. Employing security plugins that scan for vulnerable themes and enforce input validation can further reduce risk. Finally, educating developers and administrators about secure coding practices and input sanitization is essential to prevent similar vulnerabilities.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2026-02-25T12:13:39.590Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69a92061d1a09e29cbe6ce45

Added to database: 3/5/2026, 6:19:13 AM

Last enriched: 3/5/2026, 7:06:54 AM

Last updated: 3/5/2026, 3:01:04 PM

Views: 8

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses