Skip to main content

Cardea WordPress Theme EUVDEUVD-2026-96480

| CVE-2026-62065 HIGH
PHP Remote File Inclusion (CWE-98)
2026-10-10 Patchstack GHSA-2cj7-8jwr-4c3q
8.1
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Access
    Reach unauthenticated theme inclusion endpoint
  2. Exploit
    Tamper file path parameter
  3. Execution
    Include local or remote PHP file
  4. Impact
    Disclose config files or execute code

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 file-inclusion logic of the CocoBasic Cardea WordPress theme on sites running version 2.3 or earlier; no authentication is required (PR:N) and no user interaction is needed (UI:N). The key LIMITING factor is the CVSS high attack complexity (AC:H): the advisory implies a non-trivial precondition or attacker-uncontrollable circumstance (such as a specific request/path condition or configuration state) that is not spelled out in the single Patchstack reference, so reliable exploitation is not guaranteed against every default install. Risk is further bounded by the requirement that the Cardea theme specifically be installed and active, which is uncommon outside the theme's limited user base.

Impact

This is a moderate-priority issue rather than an emergency, and several signals must be weighed against each other. The CVSS 3.1 base score of 8.1 is driven by network vector (AV:N), no privileges (PR:N), and full CIA impact (C:H/I:H/A:H), consistent with CWE-98 (improper control of filename for include/require), which spans both local file inclusion and remote file inclusion that can escalate to code execution. However, the vector explicitly assigns high attack complexity (AC:H), which materially lowers real-world exploitability versus a typical AV:N/AC:L flaw - it signals a precondition or non-trivial step the attacker does not fully control. No EPSS score was supplied, the CVE is NOT on CISA KEV, and no public exploit is referenced; therefore this is 'no public exploit identified at time of analysis.' The target is the CocoBasic 'Cardea' WordPress theme (versions <= 2.3), a commercial theme with a narrow deployment footprint, so even a high-severity flaw affects a small population. Net: treat as a prioritized patch for any site actually running Cardea, but it does not warrant the same urgency as a broadly-deployed, low-complexity, actively-exploited vulnerability. No conflicting data between vector and description was found, but the AC:H precondition is undocumented in the terse advisory and should be confirmed with Patchstack/vendor.

Exploit ScenarioDerived

A remote, unauthenticated attacker crafts a request to a vulnerable file-inclusion entry point in the Cardea theme and manipulates a path/filename parameter to load an attacker-chosen file. Because CWE-98 covers remote file inclusion, a successful chain could move from reading sensitive local files (e.g., wp-config.php) to executing PHP, explaining the I:H/A:H rating; the AC:H metric indicates this requires a non-default precondition or a reliability hurdle the attacker must overcome. No public proof-of-concept is referenced, so exploitation is currently theoretical based on the advisory.

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 CocoBasic's Cardea WordPress theme (version 2.3 and earlier) lets remote attackers feed attacker-influenced input into a PHP include/require path, exposing arbitrary local files and - per the assessed vector's high integrity impact - potentially enabling code execution or file tampering if the right secondary conditions are met. The flaw needs neither authentication (PR:N) nor user interaction (UI:N), but the high attack complexity (AC:H) indicates a non-trivial precondition or configuration-dependent circumstance that the single Patchstack advisory does not spell out, so reliable exploitation against every default install is not guaranteed. Exploitation is bounded by the requirement that the Cardea theme be installed and active, there is no evidence of active exploitation (not in CISA KEV) and no public exploit identified at time of analysis, making this a moderate-priority issue rather than an emergency.

RemediationAI

No vendor-released patch was identified at time of analysis, and the only public reference is the Patchstack vulnerability entry (https://patchstack.com/database/wordpress/theme/cardea-wp/vulnerability/wordpress-cardea-theme-2-3-local-file-inclusion-vulnerability); check that advisory and the theme vendor for a fixed release before assuming a safe version exists. Because the vulnerable component is a theme, the most effective compensating control is to deactivate and remove the Cardea theme from any WordPress installation that does not strictly require it - the trade-off being the immediate loss of the theme's presentation and layout until a fixed build is available. Where the theme must remain, restrict the include-reaching request path at the edge (WAF rules that reject traversal sequences such as ../, encoded variants, and absolute or php://, data://, and file:// style wrapper payloads in theme query parameters), accepting that signature-based blocking is bypassable and requires tuning to avoid false positives on legitimate requests. Harden the PHP runtime by setting allow_url_include = Off, applying a restrictive open_basedir so theme code cannot read outside the WordPress tree, and disabling display_errors to limit the file content echoed back to the attacker; these reduce the value and reach of a successful inclusion but do not eliminate the underlying flaw, and open_basedir or disable_functions constraints can break other plugins. Finally, treat the WordPress site's file system permissions and integrity monitoring as detective controls - restrict write access to theme files under the web user and alert on unexpected modification of PHP files inside wp-content/themes, since the assessed high integrity impact implies a successful exploit could alter code, not merely read it.

Affected VersionsENISA

Cardea n/a ≤2.3

Affected Packages

euvd cardea 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 root cause class is CWE-98, improper control of a filename used in a PHP include/require statement: the theme passes insufficiently validated input into PHP's file-inclusion machinery, which can be abused for local file inclusion by supplying traversal sequences or absolute paths in a parameter that ultimately reaches include(), require(), or an equivalent wrapper. WordPress themes are ordinary PHP applications executing under the web server's user context, so any reachable theme file that builds an include path from request data is a candidate vector. The CPE cpe:2.3:a:cocobasic:cardea:*:*:*:*:*:*:*:* confirms the vendor/product pair (CocoBasic / Cardea) with the wildcard indicating the affected range as published by the reporter, Patchstack, covering version 2.3 and earlier. The assessed vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H describes a network-reachable, unauthenticated, no-interaction bug whose high attack complexity reflects an unstated precondition or attacker-uncontrollable circumstance, with scope unchanged and both confidentiality and integrity rated High - consistent with file disclosure escalating to code execution or file modification when the inclusion target is attacker-influenced. Tagging as a WordPress theme LFI/information-disclosure issue matches the PHP-based, theme-scoped nature of the defect.

Know when Cardea 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 remote request (AV:N/PR:N/UI:N); AC:H reflects the undocumented precondition; CWE-98 inclusion can yield code execution, justifying C:H/I:H/A:H with unchanged scope.

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 Cardea <= 2.3 versions.

Executive ViewAI

Why It Matters

Organizations running the CocoBasic Cardea theme (version 2.3 and earlier) on their WordPress sites face an unauthenticated local file inclusion vulnerability (CVE-2026-62065, CVSS 8.1) that could expose sensitive server files and, under specific conditions, permit code execution or content tampering. Any internet-facing site with this theme active is potentially reachable by an unauthenticated attacker without user interaction, though exploitation is not guaranteed on every install due to a non-trivial precondition. No vendor patch is currently available, and while there is no evidence of active exploitation or public exploit code, leadership should treat this as a high-priority remediation item requiring immediate interim mitigations until a fix is released.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include deactivating or removing the Cardea theme where not required, applying WAF/virtual patching rules to block local file inclusion and path traversal attempts, restricting web server file permissions, disabling risky PHP configuration options such as allow_url_include, and enhancing monitoring for anomalous file access or tampering.

Threat Intelligence Overview

EPSS Score
0.3%
Top 74% exploitable
Prevalence
Low
niche commercial WordPress theme, limited site 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