LiveActive security incident?Get immediate response
CVE Record

CVE-2025-69044: WordPress Vango theme <= 1.3.3 - Local File Inclusion vulnerability

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

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-69044 affects the WordPress Vango theme through version 1.3.3. It is a local file inclusion issue that may let an unauthenticated attacker make the site include unintended files. The published CVSS score is 8.1, high, with possible confidentiality, integrity, and availability impact. No cited source confirms active exploitation.

Executive priority

Prioritize identification of affected WordPress sites this week, especially public-facing business sites. If any use Vango <= 1.3.3, treat remediation as high priority because the issue is unauthenticated and rated high severity. Current sources do not prove active exploitation.

Technical view

The CVE describes improper control of a filename used in a PHP include/require statement, classified as CWE-98. The affected product is goalthemes Vango theme, versions up to and including 1.3.3. The CVSS vector is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, indicating remote unauthenticated reachability but high attack complexity.

Likely exposure

Exposure is limited to WordPress sites using the goalthemes Vango theme at version 1.3.3 or earlier. Sites not using this theme are not indicated as affected by the provided sources.

Exploitation context

The sources identify a local file inclusion vulnerability and high severity, but do not provide exploit details or confirm public exploitation. CISA KEV status in the bundle is false. Treat internet-facing affected WordPress sites as higher priority due to unauthenticated network attack characteristics.

Researcher notes

Evidence is limited to the CVE record and Patchstack database reference. The bundle names the weakness as PHP include/require filename control and describes local file inclusion. No patch version, exploit availability, or detailed vulnerable parameter is provided in the supplied sources.

Mitigation direction

  • Inventory WordPress sites for the Vango theme and its installed version.
  • If Vango is <= 1.3.3, check vendor or Patchstack guidance for an available fix.
  • Restrict exposure of affected sites where feasible until vendor guidance is applied.
  • Back up the site before theme updates or replacement.
  • Monitor web logs and file integrity for suspicious activity.

Validation and detection

  • Confirm whether the Vango theme is installed on each WordPress site.
  • Record the exact Vango theme version from WordPress administration or asset inventory.
  • Compare installed versions against the affected range: <= 1.3.3.
  • Review Patchstack and CVE records for updated remediation status.
  • Check whether compensating controls cover the affected site.
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-69044 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-69044Attack 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
goalthemesVangovango, 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.