Security readout for executives and security teams
Plain-English summary
CVE-2026-27076 affects the WordPress LuxeDrive theme through version 1.0. It can let an unauthenticated remote attacker include local files through unsafe PHP file inclusion handling. If your public WordPress site uses this theme, treat it as urgent because confidentiality, integrity, and availability impacts are rated high.
Executive priority
Prioritize identification this week for public WordPress sites. Remediate promptly if LuxeDrive <= 1.0 is present, especially on revenue-generating or customer-facing systems. Urgency is high, but active exploitation is not confirmed in the provided sources.
Technical view
The CVE describes CWE-98 improper filename control in PHP include/require handling, resulting in local file inclusion in Mikado-Themes LuxeDrive <= 1.0. CVSS 3.1 is 8.1 high: network exploitable, no privileges, no user interaction, high complexity, and high C/I/A impact.
Likely exposure
Exposure is limited to WordPress installations using the LuxeDrive theme through version 1.0. Internet-facing WordPress sites are the primary concern. The provided sources do not identify affected plugins, other themes, or a confirmed patched version.
Exploitation context
The source bundle does not show CISA KEV listing or cited active exploitation. Patchstack and CVE records identify the vulnerability, but no public exploit status, proof-of-concept, or exploitation campaign is provided here.
Researcher notes
Evidence is sparse: CVE and Patchstack identify LuxeDrive <= 1.0 and assign CVSS 8.1. The bundle does not provide vulnerable parameter details, exploitability proof, a fixed release, or exploitation telemetry. Avoid assuming broader Mikado-Themes exposure without additional source confirmation.
Mitigation direction
- Inventory WordPress sites for the LuxeDrive theme.
- Confirm whether any installation is version 1.0 or earlier.
- Check Patchstack and vendor guidance for fixed versions or official remediation.
- Disable or replace the theme if business use is not required.
- Restrict administrative access and keep WordPress components updated.
Validation and detection
- Review theme inventory across production, staging, and backups.
- Verify LuxeDrive version from WordPress administration or asset records.
- Check web logs for suspicious file-include or path traversal activity.
- Confirm whether a vendor-supported update or replacement has been applied.
- Track CVE, Patchstack, and KEV updates for status changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCVE-2026-27076 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.