Skip to main content

Teoro WordPress Theme CVE-2026-62068

| EUVDEUVD-2026-96483 HIGH
PHP Remote File Inclusion (CWE-98)
2026-10-10 Patchstack GHSA-vjc4-wm9v-h597
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 using Teoro theme ≤1.1
  2. Delivery
    Craft request with manipulated file-path parameter
  3. Exploit
    Bypass path handling to include local file
  4. Execution
    Disclose wp-config.php / sensitive files
  5. Impact
    Harvest database credentials

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 targets the Teoro WordPress theme (cocobasic) at versions 1.1 and below via a file-path parameter that is improperly controlled for a PHP include/require operation (CWE-98), allowing inclusion of local files such as wp-config.php. No authentication is required (PR:N) and no user interaction is needed (UI:N), but the CVSS AC:H metric indicates a limiting prerequisite: successful exploitation depends on conditions outside the attacker's control or requires specialized effort (e.g., a specific request/encoding state or environment configuration rather than a trivial parameter injection). The attack surface is limited to sites actually running this specific theme at the vulnerable version.

Impact

Signals are mixed and skew toward moderate real-world risk despite the 8.1 'High' base score. The CVSS vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N) confirms a remotely reachable, unauthenticated flaw - attractive to attackers - but the AC:H (high attack complexity) metric indicates exploitation depends on conditions outside the attacker's direct control or requires non-trivial effort, which materially dampens mass-exploitation potential. No EPSS score, CISA KEV listing, or public POC is present in the provided data, so there is no evidence of active exploitation or weaponization; this is 'no public exploit identified at time of analysis.' The claimed impact (C:H/I:H/A:H) is inconsistent with the 'Information Disclosure' / 'LFI' framing of the description: a Local File Inclusion whose primary documented effect is information disclosure would typically warrant high confidentiality but low/no integrity and availability impact - the I:H/A:H values likely reflect CWE-98's theoretical escalation to code execution rather than the demonstrated behavior, so the real impact should be verified with Patchstack. Net: a credible, vendor-reported (Patchstack) unauthenticated flaw worth patching, but the high attack complexity plus absence of KEV/EPSS/POC argues against emergency prioritization relative to lower-complexity unauthenticated bugs.

Exploit ScenarioDerived

A remote, unauthenticated attacker crafts a request to a vulnerable Teoro theme endpoint that manipulates a file path parameter to include a local file (e.g., wp-config.php) and disclose sensitive data such as database credentials. The CVSS AC:H metric means success depends on specific conditions (such as a particular request state, encoding, or deployment factor), so exploitation is not fully reliable. No public proof-of-concept is identified in the provided data.

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 Teoro WordPress theme (CocoBasic) at versions 1.1 and below lets a remote attacker induce the theme's PHP code to include a locally present file - most critically wp-config.php - exposing database credentials and salts that can be reused to take over the site. The vulnerability requires no credentials (PR:N) and no user interaction (UI:N), but the CVSS AC:H metric indicates a meaningful precondition outside the attacker's direct control (for example a specific request/encoding state or environment configuration), and exposure is limited to sites actively running this specific theme at a vulnerable version; there is no CISA KEV listing and no public exploit identified at time of analysis. The published base score is 8.1 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), while the assessed vector lowers integrity and availability impact to L, so real-world risk skews toward moderate rather than critical.

RemediationAI

No vendor-released patch was identified in the available intelligence, so the primary action is to stop running the vulnerable theme code: check the Patchstack advisory at https://patchstack.com/database/wordpress/theme/teoro-wp/vulnerability/wordpress-teoro-theme-1-1-local-file-inclusion-vulnerability?_s_id=cve for a fixed release and, if none exists, deactivate, uninstall, or replace Teoro with a maintained theme - the trade-off is an immediate change to the site's front-end appearance and any child-theme customizations must be migrated. If the theme cannot be removed, deploy targeted virtual patching: block requests whose parameters contain traversal sequences, PHP wrapper schemes such as php://filter and php://input, or filenames like wp-config.php, accepting that this both risks false positives with legitimate template paths and leaves an unpatched codebase in place; set open_basedir to confine PHP filesystem access to the WordPress root and uploads directory, understanding it may break plugins that legitimately read files elsewhere; and disable allow_url_include so the include primitive cannot be escalated to remote file inclusion (this does nothing to stop local inclusion itself). Because the exploitation outcome is disclosure of wp-config.php contents, treat any exposure as a credential compromise: rotate the database user password and regenerate WordPress authentication salts and keys in wp-config.php after removing the vulnerable theme, and review web and database logs for requests containing traversal or stream-wrapper patterns to determine whether disclosure already occurred. Note that exploitation requires an AC:H precondition, so detection by pattern matching should be tuned cautiously rather than assumed to be complete.

Affected VersionsENISA

Teoro n/a ≤1.1

Affected Packages

euvd teoro 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 a CWE-98 weakness: improper control of the filename used in a PHP include/require statement. WordPress themes such as Teoro route templates and AJAX/template-part handlers through dynamically constructed file paths, and where a request-supplied file-path parameter reaches include/require without proper validation, normalization, or an allowlist, an attacker can direct PHP to load a file from the local filesystem. Because the classic payoff is reading wp-config.php - via direct inclusion or PHP stream wrappers such as php://filter with base64 encoding to render the file contents in the response - the practical outcome is disclosure of WordPress database credentials and authentication salts, tagged by Patchstack as information disclosure. The CPE cpe:2.3:a:cocobasic:teoro:*:*:*:*:*:*:*:* identifies the affected component as the CocoBasic Teoro theme with a wildcard version, while the vendor/description data pins the vulnerable range to 1.1 and earlier. Exploitation is unauthenticated and needs no user interaction, but the AC:H rating in both the published and assessed vectors reflects an exploitation prerequisite that is not attacker-controlled, meaning a successful include is not a trivial parameter injection across every deployment; the assessed vector also reduces integrity and availability impact to Low, consistent with a read/disclosure-oriented primitive rather than guaranteed full compromise.

Know when Teoro 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

Remote unauthenticated (AV:N/PR:N); AC:H retained per vendor and LFI complexity; primary impact is file disclosure (C:H), with I:L/A:L reflecting only potential CWE-98 escalation, not demonstrated code execution.

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 Teoro <= 1.1 versions.

Executive ViewAI

Why It Matters

The Teoro (CocoBasic) WordPress theme at versions 1.1 and below contains a high-severity unauthenticated local file inclusion issue that can expose wp-config.php contents, including database credentials and salts, with potential for full site takeover. Although no public exploit identified at time of analysis and successful exploitation depends on an environmental precondition (AC:H), affected organizations should treat this as a priority because public-facing sites could be compromised, data could be exposed, and remediation may require rebuilding WordPress secrets and hardening. Leadership should care about reputational, operational, and compliance consequences for any business-critical WordPress properties using this theme.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: remove or disable the Teoro/CocoBasic theme on versions 1.1 and below and replace with a supported theme; where removal is not feasible, use WAF rules to block local file inclusion, path traversal, and php://filter attempts against wp-config.php; restrict web server and filesystem access to wp-config.php; enforce least-privilege database credentials; rotate database passwords and WordPress salts if exposure is suspected; and monitor logs for indicators of exploitation.

Threat Intelligence Overview

EPSS Score
0.3%
Top 74% exploitable
Prevalence
Low
niche commercial WordPress theme by single vendor, limited install base
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