Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in GravityWP GravityWP - Merge Tags gravitywp-merge-tags allows PHP Local File Inclusion.This issue affects GravityWP - Merge Tags: from n/a through <= 1.4.4.
Security readout for executives and security teams
Plain-English summary
CVE-2025-49271 affects the WordPress GravityWP - Merge Tags plugin through version 1.4.4. The flaw may let an attacker include local server files through PHP include/require handling. The CVSS score is high, but the supplied data says user interaction is required and attack complexity is high.
Executive priority
Treat this as a high-priority WordPress plugin exposure if the plugin is installed. Prioritize inventory and containment first because the provided sources do not name a confirmed patch version.
Technical view
The issue is classified as CWE-98: improper control of filenames in PHP include/require statements. The CVSS vector is AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H, indicating possible high confidentiality, integrity, and availability impact if successfully exploited.
Likely exposure
Exposure is limited to WordPress installations running GravityWP - Merge Tags version 1.4.4 or earlier. The bundle does not identify affected hosting configurations or a confirmed fixed version.
Exploitation context
The supplied data does not show CISA KEV listing or cited active exploitation. Exploitation is rated network-reachable with no privileges required, but high complexity and user interaction are noted in the CVSS vector.
Researcher notes
Evidence is sparse beyond CVE metadata and Patchstack’s vulnerability entry. Do not assume remote code execution, active exploitation, or a fixed release unless confirmed by vendor or updated advisory data.
Mitigation direction
Inventory WordPress sites for GravityWP - Merge Tags and record installed versions.
If version is 1.4.4 or earlier, check vendor and Patchstack guidance immediately.
Disable or remove the plugin where business need is low until a verified fix is available.
Review WordPress file permissions and hosting isolation to reduce local file exposure.
Monitor vendor, CVE, and Patchstack entries for fixed-version confirmation.
Validation and detection
Confirm whether gravitywp-merge-tags is installed on each WordPress instance.
Verify plugin version against the affected range: through 1.4.4.
Check logs for unusual plugin-triggered file access or unexpected PHP warnings.
Review file integrity and recent changes on affected WordPress hosts.
Document whether the site has compensating controls such as WAF or strict file permissions.
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.
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.
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.
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.