Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Contributor-level account
-
DeliverySend crafted request to Vino theme parameter
-
ExploitInject traversal path into PHP include
-
ExecutionServer includes targeted local file
-
ImpactSensitive file contents disclosed
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 an authenticated WordPress account at Contributor privilege level on a site running the Vino theme version 1.9 or earlier (PR:L confirms authentication is needed; the CVE title explicitly scopes this to the Contributor role). It is network-reachable with no victim interaction (AV:N/UI:N), but limited by two concrete factors: the attacker must already hold or obtain Contributor access, and the CVSS attack complexity is rated High (AC:H), meaning success depends on additional conditions such as a specific parameter, path, or server state beyond a single default request. Sites that do not grant Contributor accounts to untrusted users, or that do not run the Vino theme, are not exposed. |
| Impact | The supplied CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.5 High) shows a network-reachable but authentication-gated issue: PR:L means a Contributor-level WordPress account is required, and AC:H signals additional conditions that raise the bar beyond a trivial single request. No EPSS score, SSVC decision, KEV entry, or POC was provided in the intelligence, so the probabilistic-exploitation signal is simply absent rather than low - this should be treated as unknown, not safe. The C:H/I:H/A:H triad from Patchstack is broad for what the tags describe as 'Information Disclosure / LFI', so there is some tension: a pure file-read LFI justifies high confidentiality but the integrity/availability highs likely assume the CWE-98 include primitive can reach code execution - verify the actual impact against the Patchstack advisory before treating I/A as confirmed. Net: a genuine but not top-tier priority - meaningful for any site that grants untrusted users Contributor accounts, lower urgency for closed editorial teams. |
| Exploit ScenarioDerived | An attacker registers or compromises a low-privileged Contributor account on a WordPress site running the Vino theme, then submits a crafted request to the vulnerable theme parameter with a traversal/path value pointing at a sensitive server file such as wp-config.php, causing the theme to include and return its contents (database credentials, secret keys). No public POC was provided, and the CVSS AC:H indicates the attacker must satisfy extra conditions rather than firing a single trivial request. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 23, 2026
Local File Inclusion in the Vino WordPress theme (elated-themes) affects all versions up to and including 1.9, letting an attacker holding a low-privileged Contributor account cause the theme to include and disclose arbitrary local files (e.g. wp-config.php) on the server. No public exploit identified at time of analysis, and it is not listed in CISA KEV; the flaw was reported through Patchstack's WordPress vulnerability program. Because it requires a valid Contributor login and Patchstack rated attack complexity as high, real-world exploitation is gated behind account access rather than being fully open to the internet.
RemediationAI
No vendor-released patch version was identified at time of analysis in the provided data, so the exact fixed release cannot be cited without inventing a version - consult the Patchstack advisory (https://patchstack.com/database/wordpress/theme/vino/vulnerability/wordpress-vino-theme-1-9-local-file-inclusion-vulnerability) and the elated-themes changelog for the corrected build and upgrade to it as the primary fix once published. Until a patched version is confirmed, apply compensating controls: restrict or remove untrusted Contributor accounts and audit existing ones since exploitation requires that role (trade-off: limits guest-authoring workflows); deploy a WordPress-aware WAF such as Patchstack's virtual patch or an equivalent rule to block file-inclusion payloads and directory-traversal sequences targeting the theme's parameters (trade-off: rule tuning may cause false positives on legitimate content); and constrain PHP with open_basedir plus allow_url_include=Off and disabled PHP wrappers to cap what any inclusion can reach (trade-off: may break plugins that rely on broad filesystem access). If the theme is not actively required, deactivating it removes the exposure entirely.
Affected VersionsENISA
Affected Packages
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
The affected component is the Vino commercial WordPress theme (CPE cpe:2.3:a:elated-themes:vino), a PHP application running inside WordPress. The root cause is CWE-98, Improper Control of Filename for Include/Require Statement in a PHP Program (PHP File Inclusion): a PHP include/require path is built from attacker-influenced input without proper sanitization or allow-listing, so a user-supplied value is used to select the file that gets included. In a Local File Inclusion pattern the path resolves to files already on the host, exposing their contents; CWE-98's include/require primitive can, depending on the code path and server configuration (log poisoning, uploadable content, or PHP wrappers), escalate from disclosure toward code execution, which is why the source-assigned CVSS marks integrity and availability impact.
Know when Vino 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
AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Contributor login required so PR:L; Patchstack-noted extra conditions give AC:H; primary impact is file-read disclosure (C:H) with only incidental integrity risk (I:L) and no availability loss without confirmed RCE.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Contributor Local File Inclusion in Vino <= 1.9 versions.
Articles & Coverage 1
Executive ViewAI
The Vino WordPress theme (all versions through 1.9) contains a local file inclusion vulnerability that exposes sensitive configuration files to users with Contributor access, potentially revealing database credentials and secrets. Successful exploitation could enable attackers with a Contributor account to extract system files and escalate access to critical backend systems. With no patch currently available, immediate mitigation through access controls is essential to reduce exposure.
No vendor-released patch identified at time of analysis. Mitigations: restrict Contributor role creation to essential personnel only with administrative approval, implement detailed audit logging for all Contributor activities, conduct weekly reviews of Contributor access patterns, and establish a theme migration plan for deployment if no patch becomes available within 60 days.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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.
The vino_server_client_data_pending function in vino-server.c in GNOME Vino 2.26.1, 2.32.1, 3.7.3, and earlier, and 3.8
tinylcy Vino through 2017-12-15 allows remote attackers to cause a denial of service ("vn_get_string error: Resource tem
Vino 2.28, 2.32, 3.4.2, and earlier allows remote attackers to read clipboard activity by listening on TCP port 5900. Ra
EUVD-2026-48092
GHSA-m9g5-jr43-6grw
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB