Skip to main content

MaxiNet WordPress Theme EUVDEUVD-2025-210195

| CVE-2025-69114 HIGH
PHP Remote File Inclusion (CWE-98)
2026-06-16 Patchstack
8.1
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Recon
    Identify WordPress site running MaxiNet theme
  2. Delivery
    Probe theme endpoints for include parameter
  3. Exploit
    Submit path-traversal payload to LFI sink
  4. Install
    Read wp-config.php and secrets
  5. C2
    Authenticate to database or admin
  6. Execute
    Escalate via log poisoning or uploaded PHP
  7. Impact
    Achieve full site compromise

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 requires that the targeted WordPress site has the ThemeREX MaxiNet theme (version ≤1.2.10) installed and active so the vulnerable PHP include endpoint is reachable, and that the attacker can issue HTTP requests to the public site (no authentication needed per PR:N). The CVSS AC:H signals an additional non-default precondition - likely a specific parameter combination, theme module/widget being enabled, or a particular request method on the vulnerable AJAX/template-loader endpoint - that the attacker must satisfy; included files must also lie within PHP's open_basedir scope and the web server's read permissions, and conversion of pure file read into RCE further requires writable/loggable content (uploads, access logs, session files) reachable by path.

Impact

The CVSS 3.1 vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H scores 8.1 and is internally consistent with an unauthenticated network-reachable LFI that yields full CIA impact (config secrets, integrity via included code, and resource exhaustion). AC:H suggests the vulnerable code path requires a non-trivial precondition such as a specific parameter combination or theme feature being active, which tempers exploitability. No EPSS score, KEV listing, SSVC decision, or public POC was provided, and the only reference is the Patchstack advisory paywall stub, so real-world exploitation telemetry is unknown - the issue should be treated as a high-priority patch for sites running MaxiNet but is not yet evidenced as mass-exploited.

Exploit ScenarioDerived

A remote attacker crafts an HTTP GET or POST request to a public MaxiNet theme endpoint, supplying a traversal payload (e.g., ../../../../wp-config.php or php://filter/convert.base64-encode/resource=wp-config.php) in a vulnerable file/template parameter, and retrieves the WordPress database credentials and AUTH_KEY secrets in the response. The attacker then uses the leaked DB credentials to access the WordPress database directly or escalates to code execution by including a previously uploaded media file or a poisoned log entry.

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

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

Alert me

AnalysisAIv1 – Jun 17, 2026

Unauthenticated local file inclusion in the ThemeREX MaxiNet WordPress theme through version 1.2.10 allows remote attackers to coerce the PHP application into including arbitrary local files, exposing sensitive configuration data such as wp-config.php and potentially enabling code execution if log poisoning or uploaded content can be reached. The flaw was disclosed via Patchstack and tracked as EUVD-2025-210195; no public exploit identified at time of analysis, and no CISA KEV listing exists.

RemediationAI

No vendor-released patch identified at time of analysis; site owners should consult the Patchstack advisory at https://patchstack.com/database/wordpress/theme/maxinet/vulnerability/wordpress-maxinet-theme-1-2-10-local-file-inclusion-vulnerability and the ThemeREX changelog for any version newer than 1.2.10 and upgrade as soon as one is published. As compensating controls until a patched release is available, deploy a WAF rule (Patchstack/Wordfence virtual patch) to block path-traversal sequences and absolute paths in query parameters reaching the theme's PHP endpoints, restrict PHP open_basedir to the WordPress installation directory to limit which files can be included, disable execution of PHP in wp-content/uploads to blunt log-poisoning escalation, and as a last resort switch the active theme away from MaxiNet - each control has trade-offs: WAF rules can be bypassed with encoding tricks, open_basedir can break plugins that legitimately read shared paths, and disabling PHP in uploads can break image-processing plugins.

Affected VersionsENISA

MaxiNet n/a ≤1.2.10

Affected Packages

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

MaxiNet is a commercial WordPress theme published by ThemeREX (CPE cpe:2.3:a:themerex:maxinet). The weakness maps to CWE-98 (Improper Control of Filename for Include/Require Statement in PHP, aka 'PHP Remote File Inclusion'), which occurs when user-controllable input is passed into PHP include/require constructs without sanitization or allow-listing. In WordPress themes this typically manifests in template-loading helpers, AJAX endpoints, or shortcode handlers that accept a 'file', 'template', 'page', or similar parameter and concatenate it into an include path, allowing path traversal (../) or absolute-path references to read or execute server-side files within PHP's open_basedir scope.

Know when Maxinet 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 and unauthenticated (AV:N/PR:N); AC:H reflects the non-default precondition implied by the original vector; primary impact is file disclosure (C:H) with only secondary integrity/availability via include chaining (I:L/A:L).

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 MaxiNet <= 1.2.10 versions.

Executive ViewAI

Why It Matters

ThemeREX MaxiNet WordPress theme through v1.2.10 contains an unauthenticated local file inclusion flaw that exposes sensitive server files, including wp-config.php, to attackers seeking database credentials and security keys. Affected organizations face immediate credential disclosure and risk of unauthorized database access or system compromise through secondary exploitation paths. No public exploit has been identified; however, the absence of patched theme versions means vulnerable sites require immediate protective action.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Deploy WAF or ModSecurity rules to detect and block file inclusion attempts targeting theme components; (2) Implement strict input validation and sanitization on all theme-related parameters before file operations; (3) Disable theme on production systems or restrict to administrators only; (4) Configure web server access controls (.htaccess or equivalent) to block directory traversal patterns; (5) Enable detailed application logging and alerting on suspicious file path requests; (6) Implement file integrity monitoring on wp-config.php and configuration directories; (7) Deploy WordPress security plugins with active LFI and directory traversal detection.

Threat Intelligence Overview

EPSS Score
0.4%
Top 65% exploitable
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.4%
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