Skip to main content

Lighthouse (WordPress theme) CVE-2025-58902

| EUVDEUVD-2025-210398 HIGH
PHP Remote File Inclusion (CWE-98)
2026-07-02 Patchstack GHSA-53r2-f5ph-rxfm
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 Lighthouse theme
  2. Delivery
    Send crafted request with traversal/wrapper path
  3. Exploit
    Theme includes attacker-controlled file path
  4. Execution
    Read wp-config.php and secrets
  5. Impact
    Optionally achieve PHP code execution

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 Lighthouse theme's PHP include/require path handling and requires the vulnerable theme (<= 1.2.12) to be installed and active on a network-reachable WordPress site; per the CVSS vector (PR:N/UI:N) no authentication or user interaction is needed. The limiting factor is CVSS AC:H - success depends on specific conditions such as the vulnerable endpoint/parameter being reachable and the server allowing the traversal or PHP-wrapper technique used; full integrity/availability (code-execution) impact further depends on non-default server settings such as allow_url_include being enabled or attacker-writable content being includable, so a hardened server may limit the outcome to file disclosure only.

Impact

Signals are mixed. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, base 8.1 High) indicates a network-reachable, unauthenticated, no-user-interaction flaw with full impact, but the AC:H metric signals that exploitation depends on specific, non-trivial conditions rather than a trivial one-shot request. No EPSS score was provided, so exploitation probability cannot be quantified from this data. The vulnerability is NOT in CISA KEV and no POC/exploit reference is included, so this should be treated as 'no public exploit identified at time of analysis' - a real-but-not-emergency issue. The I:H/A:H ratings are somewhat optimistic for a pure LFI; they are justified only if the inclusion can reach writable/attacker-supplied content (true RFI) or PHP wrappers enabling execution - for a read-only LFI the practical impact is primarily confidentiality (C:H). Verify the actual sink with the Patchstack advisory before assuming code execution.

Exploit ScenarioDerived

An unauthenticated attacker sends a crafted HTTP request to the vulnerable theme endpoint with a manipulated file/path parameter using directory traversal or a PHP wrapper, causing the theme to include an unintended file and return the contents of wp-config.php (exposing database credentials and secret keys). If the server permits inclusion of attacker-controlled or uploaded content, the same primitive can be leveraged toward PHP code execution. No public POC is referenced, and the CVSS AC:H rating implies the attacker must satisfy specific conditions to reliably trigger the include.

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 – Jul 02, 2026

Unauthenticated Local File Inclusion in the AncoraThemes 'Lighthouse' WordPress theme (versions 1.2.12 and earlier, classified under CWE-98) lets remote attackers with no credentials coerce the theme's PHP include/require logic into loading attacker-influenced file paths. Because CWE-98 covers PHP remote/local file inclusion, a successful attack can disclose sensitive server files (wp-config.php, credentials) and, depending on server configuration, escalate to code execution, which is why NVD scores full C/I/A impact. There is no public exploit identified at time of analysis and the flaw is not listed in CISA KEV.

RemediationAI

Update the Lighthouse theme to the first release published after 1.2.12; however, no vendor-released patched version is identified in the available data, so operators should consult the Patchstack advisory (https://patchstack.com/database/wordpress/theme/lighthouseschool/vulnerability/wordpress-lighthouse-theme-1-2-12-local-file-inclusion-vulnerability) and the AncoraThemes/ThemeForest changelog for the exact fixed build before upgrading. As compensating controls until a fix is confirmed: deploy a WAF or Patchstack virtual patch to block directory-traversal and PHP-wrapper patterns (../, php://, data://) on the theme's request parameters; harden PHP by setting allow_url_include=Off and open_basedir to restrict includable paths (side effect: may break plugins that legitimately load external paths); and restrict or disable the specific theme endpoint/AJAX action performing the include if it is non-essential (trade-off: loss of the associated theme feature). Deny web access to sensitive files such as wp-config.php at the server layer as defense against disclosure.

Affected VersionsENISA

Lighthouse n/a ≤1.2.12

Affected Packages

euvd lighthouse 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 affected component is a WordPress theme distributed by the vendor AncoraThemes (CPE cpe:2.3:a:ancorathemes:lighthouse), marketed as a school/education theme ('lighthouseschool'). The root cause is CWE-98, Improper Control of Filename for Include/Require Statement in a PHP Program (PHP Remote/Local File Inclusion): the theme passes externally controllable input into a PHP include(), require(), or template-loading call without adequate sanitization or allow-listing. In WordPress themes this pattern typically appears in AJAX handlers, template loaders, or query-parameter-driven page renderers that build a filesystem path from user input, allowing directory traversal (../) or php:// / data:// wrapper abuse to reference unintended files.

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

Network-reachable, unauthenticated LFI (AV:N/PR:N/UI:N) with AC:H for the required inclusion conditions; C:H for file disclosure, but I/A rated Low since code execution depends on unconfirmed server conditions.

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 Lighthouse <= 1.2.12 versions.

Executive ViewAI

Why It Matters

The Lighthouse WordPress theme (v1.2.12 and earlier) contains an unauthenticated file inclusion vulnerability (CVE-2025-58902, CVSS 8.1) allowing remote attackers to read sensitive server files including database credentials stored in wp-config.php. While no public exploit identified at time of analysis, any organization using this theme faces immediate risk of credential disclosure and potential database compromise. Urgent remediation is required across all affected WordPress installations.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Immediately deactivate and remove Lighthouse theme from all WordPress installations; (2) Deploy Web Application Firewall rules to block file inclusion attack patterns (path traversal, include/require statements); (3) Disable remote file inclusion in PHP configuration (allow_url_include=Off) if operationally feasible; (4) Enable access logging and intrusion detection monitoring to identify exploitation attempts.

Threat Intelligence Overview

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