Skip to main content

Volos WordPress Theme EUVDEUVD-2026-96481

| CVE-2026-62066 HIGH
PHP Remote File Inclusion (CWE-98)
2026-10-10 Patchstack GHSA-6m8x-vgcj-67f7
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 site running Volos theme ≤1.2
  2. Delivery
    Send crafted request with path parameter
  3. Exploit
    Trigger unauthenticated local file inclusion
  4. Execution
    Read sensitive files (e.g. wp-config.php)
  5. Impact
    Potentially escalate to code execution via wrappers

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

The vulnerable input is a local-file-inclusion sink in the Volos WordPress theme at versions 1.2 and below (PHP include/require with attacker-controlled path, per CWE-98); the specific parameter and endpoint are not disclosed in the available data. No authentication is required (PR:N) and no user interaction (UI:N), making it remotely reachable against any site with the affected theme active. The key limiting factor is the high attack complexity (AC:H), indicating a non-trivial precondition - such as a specific configuration, path, timing/race, or environmental state - must be met for reliable exploitation; additionally, exploitation is scoped to sites actually running the Volos theme ≤1.2, a narrow installed base.

Impact

The input CVSS vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, base 8.1) describes a network-reachable, unauthenticated (PR:N) flaw requiring no user interaction but carrying high attack complexity (AC:H), which materially tempers the raw score - successful exploitation likely depends on a specific condition or timing rather than being trivially repeatable. No EPSS score, CISA KEV listing, or public POC was provided in the intelligence, so there is currently no public exploit identified at time of analysis and no evidence of active exploitation; the risk signals are therefore limited to the theoretical CVSS rating. CWE-98 (PHP file inclusion) legitimately justifies the C:H rating and can plausibly escalate to code execution via PHP wrappers or log poisoning, supporting the I:H/A:H impacts, though the vendor description characterizes the issue narrowly as 'Local File Inclusion' and the tags emphasize 'Information Disclosure', which suggests file-read impact is the confirmed primary effect while full integrity/availability impact is inferred from the CWE class rather than stated. Net assessment: a genuinely serious flaw for any site running the affected theme, but the combination of AC:H, no observed exploitation, and the niche footprint of a single WordPress theme places it below internet-wide emergencies - prioritize patching for affected installations but it is not a mass-exploitation priority on current evidence.

Exploit ScenarioDerived

A remote, unauthenticated attacker sends a crafted request to a Volos-theme endpoint that passes attacker-controlled input into a PHP include/require path, causing the application to read or include an arbitrary local file (e.g., wp-config.php). Because the CVSS specifies AC:H, the attacker may need to satisfy a specific precondition or win a race before the inclusion succeeds. No public proof-of-concept is identified at time of analysis.

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

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

Alert me

AnalysisAIv1 – Oct 10, 2026

Unauthenticated local file inclusion in the Volos WordPress theme (versions 1.2 and below, published by CocoBasic) allows remote attackers to influence a PHP include/require path and pull in arbitrary local files on any site running the affected theme. The vulnerability is network-reachable with no authentication and no user interaction (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, base 8.1), but the high attack complexity score indicates a non-trivial precondition - a specific configuration, path, or environmental state - must be satisfied for reliable exploitation, and the affected installed base is limited to sites actively running Volos. No public exploit code has been identified at time of analysis and there is no CISA KEV entry, so exploitation is expected to be opportunistic rather than mass-campaign driven.

RemediationAI

No vendor-released patch was identified at time of analysis, and no fixed version number is available in the provided data, so remediation must begin with operational containment. The strongest control is to deactivate and remove the Volos theme from any production WordPress installation where it is not strictly required - the obvious trade-off being loss of the site's theme layout and any customizations built on top of it, which should be staged on a maintenance window. If the theme must stay active, deploy a virtual patch at the WAF or reverse-proxy layer that blocks requests containing PHP stream wrappers and traversal sequences in query strings and POST bodies (for example php://, php://filter, data://, ../, %2e%2e%2f), accepting that signature-based rules of this kind are evadable through encoding and parameter pollution and must be tuned to avoid false positives on legitimate file-related traffic. Harden the PHP runtime by ensuring allow_url_include is Off, restricting allow_url_fopen, and setting open_basedir to the site root so that even a successful include cannot reach outside the webroot - noting open_basedir can break plugins or theme components that legitimately reference files elsewhere on disk. Restrict filesystem permissions so the web user cannot read wp-config.php backups, .env files, or log directories, and set display_errors Off to avoid leaking absolute paths that aid exploitation. Because the vulnerable parameter is undisclosed and the unauthenticated, no-user-interaction profile makes scanning easy, enable logging and alerting on suspicious include-style parameters in theme paths, and monitor the Patchstack advisory and the CocoBasic product page for a patched release to apply as soon as one is published.

Affected VersionsENISA

Volos n/a ≤1.2

Affected Packages

euvd volos 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

The flaw is classified as CWE-98, 'Improper Control of Filename for Include/Require Statement in PHP Program', the classic PHP inclusion-sink weakness in which a script passes attacker-influenced data into include, include_once, require, or require_once without validating it against an allow-list of intended files. In the Volos theme the vulnerable input is a local-file-inclusion sink with an attacker-controlled path; because WordPress themes execute PHP in the web server's context and are loaded via the theme templating system, an unfiltered parameter reaching an inclusion primitive can be used to read arbitrary files the PHP process can access (for example wp-config.php, .env files, or /etc/passwd), and under favorable conditions - such as an attacker-writable upload directory or log file that can be included - escalate to code execution, which is consistent with the assessed High confidentiality and integrity impact. The CPE string cpe:2.3:a:cocobasic:volos:*:*:*:*:*:*:*:* identifies the vendor as CocoBasic and the product as Volos with a wildcard version, matching the advisory's stated range of 1.2 and earlier. Patchstack reported the issue, and its tags (WordPress, WordPress Theme, PHP, LFI, Information Disclosure) confirm this is a theme-level PHP inclusion defect rather than a WordPress core or plugin flaw; the specific vulnerable parameter and endpoint are not disclosed, which is the main reason for the elevated AC:H rating.

Know when Volos 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 8.1 HIGH

Unauthenticated network LFI (AV:N/PR:N/UI:N) with AC:H reflecting a non-trivial precondition; CWE-98 file inclusion can read sensitive files and escalate to code execution, justifying C:H/I:H/A:H.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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 Volos <= 1.2 versions.

Executive ViewAI

Why It Matters

Any public-facing website running the Volos WordPress theme (version 1.2 or earlier, from vendor CocoBasic) carries an unauthenticated local file inclusion flaw that lets a remote attacker pull arbitrary files from the web server, potentially exposing credentials and configuration data or enabling further compromise. Because exploitation requires no login and no user action, exposure is not gated by employee behavior, though the attack requires a difficult-to-meet environmental precondition and only sites actively running this niche theme are affected. Leadership should treat this as a bounded but serious web-presence risk, since the affected software is third-party and no vendor fix currently exists, leaving mitigation to internal action.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or fully remove the Volos theme (versions 1.2 and below) from all sites; migrate to a supported WordPress theme; front the sites with a web application firewall or reverse proxy filtering path-traversal and include-path manipulation attempts; harden PHP settings to disable URL and remote file inclusion and constrain include paths; restrict filesystem read permissions for the web user; and monitor web/PHP logs for local file inclusion attempts and unexpected file access.

Threat Intelligence Overview

EPSS Score
0.3%
Top 74% exploitable
Prevalence
Low
single niche WordPress theme (Volos by cocobasic), limited deployment footprint
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.3%
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
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