Security readout for executives and security teams
Plain-English summary
CVE-2023-26005 affects the BZOTheme Fitrush WordPress theme through version 1.3.4. A vulnerable site may let an unauthenticated attacker make the application include unintended local files. The rated impact is high, but exploitation complexity is also high.
Executive priority
Treat this as a high-priority WordPress exposure review, especially for public sites using Fitrush. The absence of confirmed active exploitation lowers emergency pressure, but the potential business impact remains serious.
Technical view
The CVE describes CWE-98 improper filename control in a PHP include/require statement in Fitrush. The source records local file inclusion, CVSS 3.1 score 8.1, network attack vector, no privileges, no user interaction, high confidentiality, integrity, and availability impacts.
Likely exposure
Exposure is likely limited to WordPress sites running the BZOTheme Fitrush theme at version 1.3.4 or earlier. The bundle does not identify affected CPEs or confirm whether default installations are vulnerable.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no supplied source confirms active exploitation. The CVSS vector indicates remote unauthenticated reachability, but with high attack complexity.
Researcher notes
Evidence is limited to CVE and Patchstack metadata. The bundle does not provide vulnerable parameters, exploit details, a fixed version, or mitigation specifics, so validation should focus on asset presence, versioning, and vendor guidance.
Mitigation direction
- Inventory WordPress sites for the Fitrush theme and exact version.
- Check BZOTheme, Patchstack, and CVE guidance for an official fixed version.
- Prioritize replacement or removal if no supported fixed release is available.
- Restrict administrative changes and monitor affected sites until remediated.
Validation and detection
- Confirm whether bw-fitrush or Fitrush is installed on each WordPress site.
- Record the installed theme version and compare it to 1.3.4.
- Review web logs for suspicious requests targeting theme include paths.
- Document whether any vendor fix or mitigation has been applied.
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-2023-26005 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.