LiveActive security incident?Get immediate response
CVE Record

CVE-2025-69407: WordPress Struktur theme <= 2.5.1 - Local File Inclusion vulnerability

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Select-Themes Struktur struktur allows PHP Local File Inclusion.This issue affects Struktur: from n/a through <= 2.5.1.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-69407 affects the WordPress Struktur theme through version 2.5.1. It is a local file inclusion issue that could let an unauthenticated attacker access or manipulate server-side files under certain conditions. The CVSS score is 8.1, but exploitation complexity is rated high. No source provided confirms active exploitation.

Executive priority

Prioritize identification this week for public WordPress sites. Treat affected internet-facing sites as high risk, especially where the theme is active and business-critical. Immediate emergency response is not supported by the current evidence because active exploitation is not confirmed.

Technical view

The CVE describes improper control of a filename used in a PHP include/require statement, mapped to CWE-98. Affected software is Select-Themes Struktur for WordPress, versions up to and including 2.5.1. CVSS 3.1 vector is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.

Likely exposure

Exposure is limited to WordPress sites with the Struktur theme installed at version 2.5.1 or earlier. Sites not using this theme are not indicated as affected in the provided sources.

Exploitation context

The issue is network-accessible, requires no privileges or user interaction, and can impact confidentiality, integrity, and availability. However, attack complexity is high, and the provided sources do not report public exploitation or CISA KEV listing.

Researcher notes

The public bundle names the vulnerability and CVSS details but does not include a fixed version, proof of concept, or confirmed exploitation. The description contains both remote-file-inclusion wording and local-file-inclusion impact; rely on vendor advisories for final remediation specifics.

Mitigation direction

  • Inventory WordPress sites for the Struktur theme and version.
  • If version is 2.5.1 or earlier, check vendor or Patchstack guidance.
  • Update if a fixed version is available from the vendor.
  • Disable or replace the theme if no fix is available and risk is unacceptable.
  • Restrict administrative access and maintain current WordPress hardening controls.

Validation and detection

  • Confirm whether the Struktur theme is installed on each WordPress site.
  • Record the installed theme version and compare against <= 2.5.1.
  • Review vendor, CVE, and Patchstack pages for fix or mitigation updates.
  • Check web logs for unusual file inclusion attempts or unexpected file access.
  • Verify remediation by confirming the vulnerable theme version is no longer active.
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-69407 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-69407Attack 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
Select-ThemesStrukturstruktur, 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.