LiveActive security incident?Get immediate response
CVE Record

CVE-2025-39391: WordPress Checkout Field Visibility for WooCommerce plugin <= 1.3.0 - Local File Inclusion vulnerability

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in zamartz Checkout Field Visibility for WooCommerce checkout-field-visibility-for-woocommerce allows PHP Local File Inclusion.This issue affects Checkout Field Visibility for WooCommerce: from n/a through <= 1.3.0.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE affects a WooCommerce checkout plugin and may let an attacker make the site include local PHP files. The listed impact is high because confidentiality, integrity, and availability could all be affected. The supplied sources do not show confirmed active exploitation or a named fixed version.

Executive priority

Treat this as a high-priority web application exposure for affected WooCommerce sites, especially production checkout flows. Act quickly to identify use of the plugin and reduce exposure while waiting for confirmed vendor remediation details.

Technical view

CVE-2025-39391 is a CWE-98 filename control issue in zamartz Checkout Field Visibility for WooCommerce through 1.3.0. The CVSS 3.1 score is 7.5, with network attack vector, high complexity, no privileges required, and user interaction required. The source describes PHP Local File Inclusion via include/require handling.

Likely exposure

Exposure is limited to WordPress/WooCommerce sites using the checkout-field-visibility-for-woocommerce plugin at version 1.3.0 or older. The affected-version data in the bundle is partly inconsistent, so teams should verify installed plugin versions against vendor or Patchstack records.

Exploitation context

The bundle marks KEV as false, and no supplied source confirms active exploitation. A public Patchstack database entry exists, which increases awareness, but the sources do not provide evidence of exploitation in the wild.

Researcher notes

The source bundle describes LFI but does not include technical root-cause details, exploit conditions beyond CVSS, or a fixed version. The CVE was published on 2025-04-24 and updated on 2026-04-29. Avoid assuming active exploitation without KEV or source confirmation.

Mitigation direction

  • Inventory WordPress sites for checkout-field-visibility-for-woocommerce and record installed versions.
  • Disable or remove the plugin where version is 1.3.0 or older.
  • Check vendor and Patchstack guidance for a confirmed fixed release.
  • Prioritize mitigation on revenue-generating WooCommerce checkout sites.
  • Review backups and recovery plans before making production changes.

Validation and detection

  • Confirm whether each WooCommerce site has the affected plugin installed.
  • Compare installed versions against the reported affected range through 1.3.0.
  • Check web and PHP logs for unusual include-related errors or file access anomalies.
  • Verify whether the plugin is absent, disabled, removed, or updated after mitigation.
  • Document any uncertainty caused by inconsistent affected-version metadata.
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-39391 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
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H1.65.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2025-39391Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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
zamartzCheckout Field Visibility for WooCommercecheckout-field-visibility-for-woocommerce, 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.