Security readout for executives and security teams
Plain-English summary
CVE-2025-69120 is a high-severity flaw in the WordPress Dazzle theme up to version 1.0.0. An unauthenticated attacker may be able to include local files on the server, risking exposure or modification of sensitive data. The available sources do not confirm exploitation in the wild.
Executive priority
Treat this as a near-term website risk for any business using the Dazzle WordPress theme. It is high severity and unauthenticated, but evidence of exploitation is not provided. Prioritize inventory first, then remediate confirmed exposed sites.
Technical view
The record describes unauthenticated Local File Inclusion in ThemeREX Dazzle <= 1.0.0, mapped to CWE-98. CVSS 3.1 is 8.1 with network access, no privileges, no user interaction, high complexity, and high confidentiality, integrity, and availability impact. Public detail is limited to the CVE and Patchstack entry.
Likely exposure
Exposure is likely limited to WordPress sites running the ThemeREX Dazzle theme at version 1.0.0 or earlier. Internet-facing WordPress deployments using that theme should be treated as potentially reachable because the vulnerability is unauthenticated.
Exploitation context
The source bundle marks KEV as false, and no cited source confirms active exploitation. Public evidence does not include exploit maturity, observed campaigns, or detailed attack prerequisites beyond high attack complexity and unauthenticated network reachability.
Researcher notes
Available public detail is sparse. The CVSS vector indicates serious CIA impact but high attack complexity. Do not assume affected versions beyond Dazzle <= 1.0.0 or infer a patch version unless ThemeREX, Patchstack, or CVE records add it.
Mitigation direction
Inventory WordPress sites for the Dazzle theme and installed version.
Check ThemeREX and Patchstack for an official patched release or mitigation.
Prioritize remediation for internet-facing sites using Dazzle <= 1.0.0.
If no fix is available, consider disabling or replacing the theme after business review.
Validation and detection
Confirm whether Dazzle is installed on each WordPress instance.
Record exact theme versions and compare against <= 1.0.0 exposure.
Review web and application logs for unusual file access errors or anomalies.
Verify remediation by confirming the theme is patched, removed, disabled, or replaced.
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.