Security readout for executives and security teams
Plain-English summary
CVE-2025-69115 affects the ThemeREX LuxMed WordPress theme through version 1.2.2. It is an unauthenticated local file inclusion issue, meaning a public site using the theme could expose sensitive local files or cause broader site impact. The sources do not show active exploitation or a named fixed version.
Executive priority
High priority for any public WordPress site using LuxMed, especially healthcare-facing properties. Confirm exposure quickly, because unauthenticated file inclusion can create material confidentiality, integrity, and availability risk.
Technical view
The CVE describes an unauthenticated CWE-98 local file inclusion vulnerability in the LuxMed medicine and healthcare WordPress theme <= 1.2.2. CVSS 3.1 is 8.1 with network access, no privileges, no user interaction, high complexity, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely on internet-facing WordPress sites using the ThemeREX LuxMed theme at version 1.2.2 or earlier. Healthcare, clinic, doctor, and medical-service websites are the most plausible targets because of the theme’s market positioning.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not marked as KEV. The issue is unauthenticated and network-reachable, but CVSS lists attack complexity as high. Treat exploitation as plausible, not confirmed.
Researcher notes
Evidence is limited to the CVE and Patchstack listing in the source bundle. No exploit details, proof of exploitation, or fixed version are provided here. The CVSS vector indicates high impact but high attack complexity.
Mitigation direction
Identify any WordPress sites using the LuxMed theme.
Check ThemeREX and Patchstack for current remediation guidance.
Update the LuxMed theme if a safe version is available.
Disable or replace the theme if no trusted fix is available.
Prioritize public healthcare-related sites using this theme.
Validation and detection
Confirm installed LuxMed theme versions across WordPress estates.
Compare findings against the <= 1.2.2 affected range.
Review Patchstack and CVE records for updated fix details.
Check web and application logs for suspicious file access patterns.
Verify the theme is removed, disabled, or updated after remediation.
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.