LiveActive security incident?Get immediate response
CVE Record

CVE-2025-53207: WordPress WP Travel Gutenberg Blocks plugin <= 3.9.0 - Local File Inclusion Vulnerability

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in WP Travel WP Travel Gutenberg Blocks wp-travel-blocks allows PHP Local File Inclusion.This issue affects WP Travel Gutenberg Blocks: from n/a through <= 3.9.0.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in the WP Travel Gutenberg Blocks WordPress plugin may let an attacker cause the site to include local PHP files. For an exposed site running version 3.9.0 or earlier, the reported impact is high across confidentiality, integrity, and availability. The sources do not confirm active exploitation or a named fixed version.

Executive priority

Prioritize remediation for public WordPress sites using this plugin, especially travel or booking properties where website compromise could affect customer trust and operations. The issue is high severity, but urgency should be balanced by the absence of confirmed active exploitation in the supplied sources.

Technical view

CVE-2025-53207 is a CWE-98 filename control issue in PHP include/require handling, described as PHP Local File Inclusion in wp-travel-blocks through version 3.9.0. The CVSS 3.1 vector is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, indicating unauthenticated network reachability but high attack complexity.

Likely exposure

Exposure is likely limited to WordPress sites with the WP Travel Gutenberg Blocks plugin installed at version 3.9.0 or earlier. The bundle does not identify specific vulnerable routes, required configuration, or affected hosting environments beyond the plugin and version range.

Exploitation context

The CVE is not marked as CISA KEV in the supplied data, and the bundle provides no cited evidence of active exploitation. Treat internet-facing WordPress sites as higher priority because the CVSS vector indicates network access without authentication or user interaction.

Researcher notes

Key missing details are the vulnerable code path, triggering parameter, fixed version, and reliable non-invasive validation method. Do not assume remote code execution or active exploitation from the bundle alone. Use vendor or Patchstack updates to confirm remediation guidance.

Mitigation direction

  • Inventory WordPress sites for the wp-travel-blocks plugin and installed version.
  • Check WP Travel and Patchstack guidance for a fixed release or vendor workaround.
  • Disable or remove the plugin where it is not business-critical.
  • Prioritize exposed public sites running version 3.9.0 or earlier.
  • Monitor vendor advisories before re-enabling affected deployments.

Validation and detection

  • Confirm whether WP Travel Gutenberg Blocks is installed on each WordPress site.
  • Record plugin versions and flag version 3.9.0 or earlier.
  • Review web logs for unusual requests targeting plugin paths or include-related errors.
  • Check whether the CVE appears in KEV before closure.
  • Document remediation status and any compensating controls used.
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-53207 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-53207Attack 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
WP TravelWP Travel Gutenberg Blockswp-travel-blocks, 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.