LiveActive security incident?Get immediate response
CVE Record

CVE-2025-69071: WordPress TanTum theme <= 1.1.13 - Local File Inclusion vulnerability

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

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-69071 affects the WordPress TanTum theme by AncoraThemes through version 1.1.13. A flaw in how PHP files are included can allow local file inclusion. For a business, exposed WordPress sites using this theme may risk sensitive file disclosure, site modification, or disruption. Public sources do not show active exploitation.

Executive priority

Prioritize any public WordPress site using TanTum <= 1.1.13. The rating is high because successful exploitation could affect confidentiality, integrity, and availability. No active exploitation is cited, so urgency should be driven by exposure and business criticality.

Technical view

The issue is CWE-98: improper control of a filename used in PHP include/require logic. The CVE describes PHP Local File Inclusion in TanTum <= 1.1.13. CVSS 3.1 is 8.1: network reachable, unauthenticated, no user interaction, high complexity, and high confidentiality, integrity, and availability impact.

Likely exposure

Internet-facing WordPress sites running the AncoraThemes TanTum theme through version 1.1.13 are the primary exposure. Sites not using this theme are not indicated as affected by the provided sources.

Exploitation context

The CVSS vector indicates remote, unauthenticated exploitation may be possible without user interaction, but with high attack complexity. The source bundle does not cite proof-of-concept details, exploitation in the wild, or CISA KEV listing.

Researcher notes

Evidence is limited to the CVE and Patchstack database reference. The affected range is stated as TanTum through 1.1.13, but the bundle does not provide patched-version details, exploit conditions, vulnerable parameters, or proof-of-concept material.

Mitigation direction

  • Inventory WordPress sites for the TanTum theme and record installed versions.
  • If TanTum is <= 1.1.13, check AncoraThemes and Patchstack for vendor guidance.
  • Apply a vendor-provided fixed version if available.
  • If no fix is available, consider disabling or replacing the theme.
  • Back up the site before theme changes or updates.
  • Restrict administrative access and keep WordPress, plugins, and themes updated.

Validation and detection

  • Confirm whether the TanTum theme is installed on each WordPress instance.
  • Verify the TanTum version is greater than 1.1.13 or otherwise vendor-confirmed safe.
  • Review web logs for unusual file path or include-related requests.
  • Check file integrity and recent changes on affected WordPress sites.
  • Monitor the CVE record and Patchstack entry for updated 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-69071 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-69071Attack 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
AncoraThemesTanTumtantum, 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.