LiveActive security incident?Get immediate response
CVE Record

CVE-2025-69397: WordPress Tint theme <= 1.7 - Local File Inclusion vulnerability

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

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-69397 affects the ThemeREX Tint WordPress theme through version 1.7. It may let an unauthenticated remote attacker make the site include local files. Business risk is high because successful exploitation could expose sensitive data or affect site integrity and availability. Public sources provided do not show known active exploitation.

Executive priority

Treat this as a high-priority WordPress exposure if Tint is present. First determine whether the theme exists in your environment. If it does, seek vendor remediation or remove the theme where feasible. No cited source currently confirms active exploitation, but the potential impact is significant.

Technical view

The issue is improper control of filenames in a PHP include/require statement, mapped to CWE-98. The CVSS 3.1 score is 8.1 high, with network attack vector, no privileges, no user interaction, high complexity, and high confidentiality, integrity, and availability impacts.

Likely exposure

Exposure is likely limited to WordPress sites with the ThemeREX Tint theme installed at version 1.7 or earlier. The provided data does not confirm whether inactive installations are exploitable, so vulnerability managers should inventory all installations and validate theme status and version.

Exploitation context

The CVSS vector indicates remote, unauthenticated exploitation without user interaction, but with high attack complexity. The source bundle does not include exploit details, proof-of-concept status, or evidence of active exploitation. The CVE is not listed as KEV in the provided data.

Researcher notes

Evidence is limited to CVE metadata and Patchstack’s vulnerability entry. The affected range is stated as Tint through <= 1.7. No fixed version, exploit availability, or detailed vulnerable parameter is provided in the supplied sources, so avoid assumptions beyond confirmed product and version scope.

Mitigation direction

  • Identify all WordPress sites with the ThemeREX Tint theme installed.
  • Check ThemeREX and Patchstack guidance for a fixed version or vendor workaround.
  • Update Tint if a fixed version is available from the vendor.
  • Remove or disable the theme where it is unnecessary or unsupported.
  • Increase monitoring for suspicious file access patterns on affected sites.

Validation and detection

  • Confirm whether Tint is installed on each WordPress instance.
  • Record the installed Tint version and compare it to <= 1.7.
  • Review vendor and Patchstack advisories for current remediation status.
  • Check security logs for unusual local file inclusion indicators.
  • Prioritize internet-facing sites and business-critical WordPress properties.
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-69397 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-69397Attack 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
ThemeREXTinttint, 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.