Skip to main content

Backhoe WordPress Theme EUVDEUVD-2026-96487

| CVE-2026-62075 HIGH
PHP Remote File Inclusion (CWE-98)
2026-10-10 Patchstack GHSA-qvmm-v8hf-wfx2
8.1
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Access
    Send crafted HTTP request
  2. Exploit
    Manipulate file-path parameter
  3. Execution
    Trigger PHP local file inclusion
  4. Impact
    Disclose sensitive file contents

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

Requires network access to a WordPress site running the Backhoe theme version 2.0 or earlier, reachable via a request parameter that controls a file path passed to a PHP include/require. The CVSS vector reports PR:N/UI:N (no authentication and no user interaction per supplied data), but AC:H indicates a required condition outside the attacker's control - the specific vulnerable parameter, endpoint, or configuration is not named in the description and must be derived from the Patchstack advisory. Exploitation is limited to installations of this specific, low-popularity theme; sites not using Backhoe or already on a patched release are unaffected.

Impact

This is an unauthenticated Local File Inclusion (CWE-98) in the WordPress 'Backhoe' theme (versions <= 2.0), reported by Patchstack. The input CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, base 8.1) indicates network-reachable, no-authentication, no-user-interaction exploitation, which raises nominal severity. However, the signals conflict in two ways that temper real-world priority: (1) AC:H means the attacker must meet a condition outside their control, reducing reliability of exploitation; and (2) Patchstack tags the issue 'Information Disclosure'/'LFI', which points to a primarily confidentiality impact, yet the supplied vector asserts full I:H and A:H - the integrity/availability claims are not substantiated by the description and should be verified (CWE-98 file inclusion CAN escalate to code execution if attacker-controlled PHP can be included, but nothing here confirms that). No EPSS score, no CISA KEV listing, and no public exploit were provided, so there is no public exploit identified at time of analysis. Net: a genuinely interesting unauthenticated flaw, but tempered by AC:H, an obscure affected product, and absence of any exploitation evidence - treat as a patch-soon item rather than an emergency, prioritizing any publicly exposed sites running this specific theme.

Exploit ScenarioDerived

A remote, unauthenticated attacker crafts an HTTP request to a vulnerable Backhoe theme endpoint that supplies a file-path parameter, causing the PHP application to include a local file (e.g., wp-config.php or other sensitive files) and disclose its contents. The CVSS AC:H indicates exploitation depends on a condition the attacker does not fully control, so success may require specific deployment circumstances. No public proof-of-concept was provided in the intelligence sources.

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 WordPress Backhoe theme (versions 2.0 and earlier, vendor 'mymoun') lets remote attackers cause a server-side PHP include/require construct to load a file path they influence, exposing sensitive local files such as wp-config.php and disclosed configuration data. The supplied CVSS vector is AV:N/AC:H/PR:N/UI:N, and the independent assessment scores confidentiality only (C:H/I:N/A:N), so the practical impact is information disclosure rather than code execution or data modification, with the high attack-complexity component reflecting an unnamed precondition (the specific vulnerable parameter, endpoint, or environment configuration) that must be derived from the Patchstack advisory. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; exploitation is limited to sites actually running this low-popularity theme, and sites on a patched release or not using Backhoe are unaffected.

RemediationAI

No vendor-released patch was identified at time of analysis, so the primary action is to stop running the vulnerable code: if Backhoe is not the active theme, deactivate and delete it from wp-content/themes entirely (removing unused themes also eliminates the exposure and has no functional trade-off), and if it must remain active, treat the site as exposed until a fixed release appears and monitor the Patchstack advisory at https://patchstack.com/database/wordpress/theme/backhoe/vulnerability/wordpress-backhoe-theme-2-0-local-file-inclusion-vulnerability?_s_id=cve plus the vendor's WordPress.org theme page for an update, then upgrade to the first release that explicitly addresses the LFI. Interim compensating controls include restricting PHP include/require of remote-style or filter-style wrapper input by disabling allow_url_include and, where the application permits, allow_url_fopen in php.ini (side effect: other code relying on remote or stream-wrapper file access may break), hardening open_basedir to confine readable paths and reducing the value of any traversed file read (side effect: legitimate file access outside the configured roots will fail), and deploying WAF or reverse-proxy rules that reject requests whose query/body parameters contain path traversal sequences such as ../, encoded variants (%2e%2e%2f), or php://, data:, and file: wrappers targeting theme PHP endpoints; note that these are signature-based and can be bypassed by encoding tricks. Finally, review web server access logs for anomalous requests to Backhoe theme files and rotate any credentials or salts that may have been exposed through wp-config.php disclosure, since the assessed impact is confidentiality-only.

Affected VersionsENISA

Backhoe n/a ≤2.0

Affected Packages

euvd backhoe 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 Filename for Include/Require Statement in PHP Program (traditionally 'PHP Remote File Inclusion'), the same weakness family that underlies PHP local file inclusion: a theme PHP template builds an include/require (or equivalent wrapping helper such as include_once/require_once) from a variable that is populated from an HTTP request parameter rather than from a server-side allowlist. Because WordPress themes execute in the same PHP process as core and plugins, any path traversal sequence or PHP stream wrapper that survives validation can pull arbitrary readable files from the filesystem into the response, and in some deployments inclusion of attacker-controlled or attacker-readable content can escalate beyond simple disclosure. The CPE cpe:2.3:a:mymoun:backhoe:*:*:*:*:*:*:*:* identifies the affected code as the Backhoe theme distributed through the WordPress theme ecosystem, whose reliance on legacy PHP include patterns and PHP-only delivery makes it a recurring target for LFI-style bugs; the AV:N/PR:N/UI:N portion of the vector indicates the request can be issued directly over the network without credentials or victim interaction, while AC:H signals that a configuration- or input-dependent condition must be satisfied for a successful exploit.

Know when Backhoe 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 5.9 MEDIUM

Unauthenticated network LFI keeps AV:N/PR:N/UI:N and AC:H per source; impact assessed as confidentiality-only (C:H, I:N, A:N) because Patchstack classifies it as Information Disclosure, not code execution.

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

Executive ViewAI

Why It Matters

The WordPress Backhoe theme (versions 2.0 and earlier, vendor 'mymoun') contains an unauthenticated local file inclusion flaw that can expose sensitive server files, most critically wp-config.php, which holds database credentials and authentication salts for the affected site. Any organization running this low-popularity theme on an internet-facing WordPress installation is exposed without needing to authenticate, and because the vulnerability is unauthenticated and no vendor patch exists, leadership should treat this as an unresolved risk to website and back-end database integrity. Exploitation has not been confirmed in the wild and no public exploit code is currently identified, so the immediate priority is inventory and containment rather than emergency incident response.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or remove the Backhoe theme; block traversal-style and file-path parameters at the WAF or reverse proxy; harden server configuration to deny direct web access to wp-config.php and other configuration files; rotate database credentials and WordPress salts that may have been disclosed; restrict the affected site's outbound and filesystem read scope; monitor logs for anomalous include/require or path traversal attempts.

Threat Intelligence Overview

EPSS Score
0.3%
Top 74% exploitable
Prevalence
Rare
obscure single WordPress theme (vendor mymoun), minimal real-world 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