Security readout for executives and security teams
Plain-English summary
CVE-2025-69117 affects WordPress sites using the ThemeREX Ingenioso theme up to version 1.14.0. The issue may let an unauthenticated remote attacker include local files on the server. That can expose sensitive data and, depending on environment, affect integrity and availability.
Executive priority
Treat this as a high-priority web exposure issue for any public WordPress site using Ingenioso. Prioritize asset discovery, version verification, and vendor-guided remediation before assuming the risk is addressed.
Technical view
The CVE describes an unauthenticated Local File Inclusion vulnerability in Ingenioso <= 1.14.0, categorized as CWE-98. CVSS 3.1 is 8.1 with network attack vector, high complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely limited to WordPress installations running the Ingenioso theme at version 1.14.0 or earlier. The bundle does not identify other affected ThemeREX products or specific vulnerable endpoints.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Public exploitability detail is limited here, but the unauthenticated network-accessible nature makes internet-facing WordPress sites higher priority.
Researcher notes
Evidence supports unauthenticated LFI in Ingenioso <= 1.14.0 with CVSS 8.1. The bundle does not include proof-of-concept details, endpoint paths, exploit telemetry, or a named patched version, so validation should remain inventory- and vendor-advisory based.
Mitigation direction
Inventory WordPress sites for the Ingenioso theme and installed version.
Check ThemeREX and Patchstack guidance for a fixed release or mitigation.
Update the theme if a vendor-supported fixed version is available.
If no fix is available, consider disabling or replacing the theme.
Limit server file permissions to reduce impact from local file exposure.
Monitor web logs for suspicious requests targeting theme paths.
Validation and detection
Confirm whether Ingenioso is installed on each WordPress site.
Record the exact theme version and compare it with <= 1.14.0.
Review vendor and Patchstack advisories for remediation status.
Check security monitoring for unusual file access patterns.
Verify mitigated sites no longer run an affected theme version.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-98: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-98 · source CWE mapping
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.