Security readout for executives and security teams
Plain-English summary
CVE-2025-69161 is a high-severity issue in the WordPress Snowy theme. Public records describe unauthenticated local file inclusion in Snowy versions up to 1.13. A vulnerable public WordPress site could face serious data, integrity, and availability risk, but the provided sources do not show active exploitation.
Executive priority
Treat this as a near-term web exposure issue. It is not confirmed as actively exploited in the provided sources, but unauthenticated access and high potential impact justify prompt inventory and remediation planning for public WordPress assets.
Technical view
The CVE describes CWE-98 local file inclusion in ThemeREX Snowy for WordPress, reported against versions <= 1.13. The CVSS 3.1 score is 8.1 with network access, no privileges, no user interaction, high attack complexity, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely on internet-facing WordPress sites that have the Snowy theme installed at version 1.13 or earlier. The source bundle does not identify affected CPEs or a confirmed fixed release.
Exploitation context
The source bundle marks KEV as false, and no supplied source states exploitation in the wild. The issue is still important because it is unauthenticated and network reachable, although the CVSS vector rates attack complexity as high.
Researcher notes
Evidence is limited to CVE and Patchstack metadata. Do not assume exploit availability, affected CPEs, or a fixed version from the supplied bundle. Validate against live vendor or Patchstack guidance before closure.
Mitigation direction
Inventory WordPress sites for the Snowy theme and installed version.
Check ThemeREX and Patchstack guidance for an official fixed version or workaround.
If Snowy is unnecessary, disable or remove it from production sites.
Restrict administrative access and keep WordPress, themes, and plugins current.
Prioritize remediation for public sites handling sensitive data or transactions.
Validation and detection
Confirm whether each WordPress site has Snowy installed.
Record the Snowy version and flag versions 1.13 or earlier.
Check Patchstack and vendor advisories for updated remediation details.
Review web logs for unusual theme-related file access patterns.
Verify remediation by confirming the theme is updated, disabled, or removed.
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.