Security readout for executives and security teams
Plain-English summary
CVE-2025-69149 is a high-severity unauthenticated local file inclusion issue in the ThemeREX Top Dog WordPress theme, reported for versions up to 1.0.5. A successful attack could expose or affect server-side files. Business urgency depends on whether any public WordPress site uses this theme version.
Executive priority
Treat as high priority for any public WordPress site using Top Dog <= 1.0.5. If the theme is absent, risk is low for that asset. If present, prioritize confirmation, vendor guidance, and removal or update planning.
Technical view
The source bundle describes CWE-98 local file inclusion in WordPress theme package top-dog, with CVSS 8.1. The vector is network-accessible, unauthenticated, and requires no user interaction, but has high attack complexity. Confidentiality, integrity, and availability impacts are rated high.
Likely exposure
Likely exposure is limited to WordPress sites running ThemeREX Top Dog version 1.0.5 or earlier. The provided affected data does not list CPEs and marks default status as unaffected, so asset confirmation is necessary.
Exploitation context
The bundle does not report active exploitation, and KEV status is false. Patchstack and CVE references confirm the vulnerability entry, but no exploit activity, patch version, or workaround details are included in the provided evidence.
Researcher notes
Evidence is sparse. The source bundle establishes unauthenticated LFI, CWE-98, CVSS 8.1, and affected theme naming, but does not provide vulnerable parameters, fixed release, mitigation, or exploitation evidence. Avoid assuming exploitability beyond the published CVSS and vulnerability description.
Mitigation direction
Inventory WordPress sites for the ThemeREX Top Dog theme.
Confirm whether any installed Top Dog version is 1.0.5 or earlier.
Remove or disable the theme where it is not business-critical.
Check ThemeREX, Patchstack, and CVE records for fixed-version guidance.
Prioritize backups and monitoring for exposed WordPress hosts.
Validation and detection
Review WordPress theme inventory for package name top-dog.
Record installed Top Dog versions across production and staging.
Check web and application logs for suspicious unauthenticated file access attempts.
Verify whether vendor guidance names a patched version or workaround.
Track CVE and Patchstack updates for corrected affected-version details.
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.