LiveActive security incident?Get immediate response
CVE Record

CVE-2025-69067: WordPress Tails theme <= 1.4.12 - Local File Inclusion vulnerability

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

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-69067 affects the WordPress Tails theme by AncoraThemes through version 1.4.12. A remote, unauthenticated attacker may be able to make the site include unintended local files. The reported impact is high across confidentiality, integrity, and availability, but exploitation complexity is rated high.

Executive priority

Prioritize identification and remediation for public WordPress sites using Tails. Treat confirmed affected installations as high priority because successful exploitation could expose files or affect site integrity, even though current public evidence does not show active exploitation.

Technical view

The issue is classified as CWE-98: improper control of filename in a PHP include/require statement, resulting in local file inclusion. The CVSS 3.1 score is 8.1 with vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Public sources identify affected Tails theme versions as up to and including 1.4.12.

Likely exposure

Exposure is limited to WordPress sites using the AncoraThemes Tails theme at version 1.4.12 or earlier. The provided sources do not identify affected hosting configurations, vulnerable parameters, or whether inactive installed themes are exploitable.

Exploitation context

No provided source states active exploitation, and the CVE is not marked as CISA KEV. The flaw is remotely reachable and unauthenticated per CVSS, but attack complexity is high. Public source details are limited, so real-world exploitability should be verified against vendor or Patchstack guidance.

Researcher notes

Evidence is sparse beyond the CVE and Patchstack listing. Do not assume a fixed version or specific exploit path from the supplied data. Validate affected code paths only in authorized environments and track the advisory for additional technical detail.

Mitigation direction

  • Inventory WordPress sites for the AncoraThemes Tails theme.
  • Identify Tails theme versions and flag 1.4.12 or earlier.
  • Check AncoraThemes and Patchstack for official update or mitigation guidance.
  • Remove unused copies of the Tails theme where operationally safe.
  • Restrict administrative access and monitor WordPress file access anomalies.

Validation and detection

  • Confirm whether the Tails theme is installed on each WordPress site.
  • Record the installed Tails theme version from trusted asset data.
  • Compare installed versions against the affected range: through 1.4.12.
  • Review vendor and Patchstack advisories for fixed versions or compensating controls.
  • Check logs for unusual requests targeting theme PHP include paths.
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-69067 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-69067Attack 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
AncoraThemesTailstails, 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.