LiveActive security incident?Get immediate response
CVE Record

CVE-2025-69070: WordPress Tornados theme <= 2.1 - Local File Inclusion vulnerability

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in AncoraThemes Tornados tornados allows PHP Local File Inclusion.This issue affects Tornados: from n/a through <= 2.1.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-69070 affects the AncoraThemes Tornados WordPress theme through version 2.1. It can let an unauthenticated attacker abuse file-inclusion logic and potentially read, alter, or disrupt site data. The published CVSS score is 8.1, but attack complexity is rated high. No cited source indicates active exploitation.

Executive priority

Treat as a high-priority WordPress exposure if Tornados is deployed. Prioritize inventory first, because business urgency depends on whether the theme is present. No active exploitation is cited, but potential impact is high if a vulnerable site is reachable.

Technical view

The issue is improper control of a filename used in a PHP include/require statement, mapped to CWE-98. The CVE description calls the impact PHP Local File Inclusion in Tornados <= 2.1. CVSS 3.1 is 8.1 with network attack vector, no privileges, no user interaction, high complexity, and high confidentiality, integrity, and availability impact.

Likely exposure

WordPress sites using the AncoraThemes Tornados theme version 2.1 or earlier should be reviewed. Exposure details beyond the affected theme and version range are not provided in the source bundle.

Exploitation context

The vulnerability is remotely reachable according to the CVSS network vector and requires no privileges or user interaction, but has high attack complexity. CISA KEV status is false in the provided data, and no supplied source states active exploitation.

Researcher notes

Evidence is limited to the CVE record and Patchstack database reference. The affected range is stated as Tornados through <= 2.1, while the structured affected entry appears sparse. Do not assume a patch exists from the provided sources; verify with vendor or Patchstack updates.

Mitigation direction

  • Identify WordPress sites using the Tornados theme.
  • Check whether Tornados version is 2.1 or earlier.
  • Review AncoraThemes and Patchstack guidance for a fixed version or official workaround.
  • If no safe version is available, consider replacing or removing the theme.
  • Monitor vendor and CVE records for updates.

Validation and detection

  • Confirm Tornados theme presence and version from WordPress asset inventory.
  • Compare detected versions against the affected range: <= 2.1.
  • Review web logs for unusual requests targeting theme file paths.
  • Verify any remediation by confirming the vulnerable theme is updated, removed, or replaced.
  • Track Patchstack and CVE updates for clarified remediation details.
Prepared
Confidence
medium
Sources
3

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-69070 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline 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.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2025-69070Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AncoraThemesTornadostornados, 0unaffected
Weakness

CWE details

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.