Security readout for executives and security teams
Plain-English summary
This issue affects the WordPress Tipsy theme up to version 1.1. An unauthenticated attacker may be able to make the site include local server files, which can expose sensitive data or disrupt the site. The public bundle rates it high at CVSS 8.1, but it does not show known active exploitation or a named fix.
Executive priority
Treat as a high-priority WordPress exposure review. Prioritize public-facing sites using Tipsy, because the issue requires no login and has high potential impact, even though exploitation evidence is not currently cited.
Technical view
CVE-2025-69173 is an unauthenticated Local File Inclusion vulnerability in ThemeREX Tipsy for WordPress, reported for versions up to 1.1. The CVSS 3.1 vector is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, indicating network reachability, no credentials, high complexity, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely on WordPress sites with the Tipsy theme installed, especially version 1.1 or earlier. The bundle does not prove whether inactive installations are exploitable, so teams should inventory both active and installed copies.
Exploitation context
The source bundle marks KEV as false and provides no cited evidence of active exploitation. The vulnerability is serious because it is unauthenticated and may affect server-side file handling, but available public detail is limited.
Researcher notes
Public details are sparse. The key confirmed facts are product, theme version boundary, unauthenticated LFI class, CWE-98 mapping, and CVSS vector. Do not assume a patch, exploit availability, or affected code path without vendor or VDB confirmation.
Mitigation direction
Inventory WordPress sites for the Tipsy theme and version.
Check ThemeREX and Patchstack guidance for a fixed release or vendor workaround.
If no fix exists, disable or remove Tipsy after change-control review.
Limit server file permissions for WordPress and theme directories.
Monitor web logs for suspicious requests targeting Tipsy theme paths.
Validation and detection
Confirm whether Tipsy is installed, active, and at version 1.1 or earlier.
Compare findings against the CVE Program and Patchstack entries.
Review access logs for unusual file-include probes against theme endpoints.
Verify any update, removal, or disablement did not break site functionality.
Document remaining exposure where vendor guidance is unavailable.
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
0ADP providers
2Source links
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.