Skip to main content

WineShop WordPress Theme EUVDEUVD-2025-210178

| CVE-2025-69163 HIGH
PHP Remote File Inclusion (CWE-98)
2026-06-16 Patchstack
8.1
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify WordPress sites using WineShop theme
  2. Delivery
    Probe theme endpoints for file/template parameters
  3. Exploit
    Inject traversal payload via crafted HTTP request
  4. Execution
    Trigger PHP include of attacker-chosen file
  5. Persist
    Read wp-config.php or execute poisoned log/upload
  6. Impact
    Exfiltrate database credentials and pivot to admin

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V5 - File Handling File inclusion prevention, allowlisting
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Command and Control

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires a target WordPress site running the ThemeREX WineShop theme at version 3.17 or earlier as the active theme, with the vulnerable theme endpoint reachable over HTTP/HTTPS. No authentication, user interaction, or admin role is needed (PR:N/UI:N), but the CVSS AC:H rating indicates a non-trivial condition - likely specific encoding, path traversal sequence, or chaining with a writable file (log, session, or upload) to reach high-impact outcomes such as code execution. Sites where the theme is installed but inactive, or where PHP allow_url_include is disabled and open_basedir restricts file access, face significantly reduced impact.

Impact

The CVSS 3.1 score of 8.1 (High) with vector AV:N/AC:H/PR:N/UI:N reflects a remotely reachable, unauthenticated flaw with high attack complexity and full CIA impact - consistent with LFI that requires some condition (e.g., specific parameter, encoding, or null byte handling) to be met. The high attack complexity (AC:H) and the lack of any public PoC or CISA KEV entry suggest this is not currently a mass-exploitation target, but the unauthenticated nature (PR:N) on a public-facing WordPress theme makes it attractive once exploitation details surface via the Patchstack advisory. EPSS data and POC availability are not provided in the input, so probability of exploitation cannot be numerically quantified. The CVSS-stated A:H (availability impact) is somewhat aggressive for a pure LFI primitive; verify with the Patchstack advisory whether RCE escalation is demonstrated.

Exploit ScenarioDerived

An unauthenticated remote attacker sends a crafted HTTP request to a vulnerable WineShop theme endpoint with a manipulated file or template parameter pointing at a sensitive local path (e.g., wp-config.php or /etc/passwd) or at attacker-controlled content placed in logs, uploads, or session files. Successful inclusion discloses credentials and database secrets and, when chained with log poisoning or uploaded media containing PHP, results in code execution as the web server user. No public exploit identified at time of analysis, but Patchstack disclosure typically precedes scanner signatures within days.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 16, 2026

Unauthenticated Local File Inclusion in the WineShop WordPress theme versions 3.17 and earlier allows remote attackers to include and execute arbitrary local files on the server via crafted requests. The flaw stems from improper control of filename for include/require (CWE-98) and carries a CVSS 8.1 (High) with full confidentiality, integrity, and availability impact, though no public exploit identified at time of analysis.

RemediationAI

No vendor-released patch identified at time of analysis; the Patchstack advisory (https://patchstack.com/database/wordpress/theme/wineshop/vulnerability/wordpress-wineshop-theme-3-17-local-file-inclusion-vulnerability) lists affected versions as ≤3.17 without naming a fixed release. Site operators should monitor ThemeREX for a patched theme version above 3.17 and apply it immediately when published. As compensating controls, deploy a WordPress WAF rule (Patchstack, Wordfence, or ModSecurity) to block requests containing directory-traversal patterns (../, %2e%2e, php://, file://) against theme endpoints, restrict PHP open_basedir to the WordPress document root to limit file inclusion scope (side effect: may break plugins that legitimately access /tmp or shared paths), disable allow_url_include in php.ini to prevent escalation to RFI, and consider temporarily switching to a default WordPress theme on high-risk sites until a fix ships.

Affected VersionsENISA

WineShop n/a ≤3.17

Affected Packages

euvd wineshop no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

WineShop is a commercial WordPress theme developed by ThemeREX (CPE: cpe:2.3:a:themerex:wineshop) targeting wine shop and e-commerce sites. The vulnerability is classified as CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program, a.k.a. PHP Remote File Inclusion), meaning user-controlled input is passed unsanitized into a PHP include() or require() call. In WordPress theme contexts this typically arises from AJAX handlers, theme template loaders, or shortcode parameters that accept a file path or template name from request data. Once a local path is included, the PHP interpreter executes it, which can be chained with log poisoning, PHP session files, or uploaded media to achieve code execution beyond simple file disclosure.

Know when Wineshop gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 8.1 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.0 HIGH

Network-reachable unauthenticated LFI (AV:N/PR:N/UI:N) with AC:H reflecting non-trivial conditions; C:H for file disclosure, I:L/A:L since RCE escalation is not confirmed in available data.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Unauthenticated Local File Inclusion in WineShop <= 3.17 versions.

Executive ViewAI

Why It Matters

The WineShop WordPress theme (versions 3.17 and earlier) contains an unauthenticated Local File Inclusion vulnerability enabling remote attackers to read and execute arbitrary server files without credentials, with no public exploit identified at time of analysis. Organizations using this theme face immediate risk of data theft and complete server compromise, with full impact to confidentiality, integrity, and availability. The absence of a vendor patch creates critical urgency for all affected WordPress installations.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Deactivate and replace affected theme immediately; (2) Deploy WAF rules blocking file inclusion attack patterns; (3) Restrict file permissions on wp-config.php and sensitive configuration files; (4) Disable PHP functions include/require/file_get_contents where not required; (5) Monitor and analyze server logs for exploitation indicators; (6) Subscribe to WineShop security advisories for patch notification when available.

Threat Intelligence Overview

EPSS Score
0.5%
Top 63% exploitable
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.5%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Very High
Technical Impact
Total

Priority Score

40
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +40
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Local File Inclusion vulnerabilities occur when an application accepts user-controlled input to specify which file should be loaded or executed, typically through functions like PHP's `include()`, `require()`, or `fopen()`.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy