Threat Intelligence / CVE / CVE-2025-39391

CVE-2025-39391 — zamartz Checkout Field Visibility for WooCommerce

CVSS v3.1 7.5 (HIGH) · EPSS 0.6% (higher than 47.6% of all scored CVEs) · Priority 5.7/10 · Published 2025-04-24

As of 2026-04-29, CVE-2025-39391 is a HIGH-severity vulnerability in zamartz Checkout Field Visibility for WooCommerce, CVSS v3.1 7.5, EPSS 0.6% (47.6th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2025-39391, most recently “313 Team Iran-Aligned Hacktivists Weaponize Agentic AI, Mirai-Derived Botnets, and Prompt Injection Against E-Commerce APIs (CVE-2025-39391)”.

Last updated: 2026-04-29

What is CVE-2025-39391?

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.

The record classifies CVE-2025-39391 under weakness class CWE-98. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs a user to take an action first, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 525 days ago.

Severity and exploitation probability

CVSS v3.1 base score
7.5 — HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS (FIRST)
0.6% probability of exploitation in the next 30 days, higher than 47.6% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
5.7/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2025-04-24, last modified 2026-04-29

Is CVE-2025-39391 being exploited?

No public exploitation evidence for CVE-2025-39391 is recorded in the sources Threadlinqs tracks — CISA KEV, Exploit-DB, public proof-of-concept repositories and ProjectDiscovery Nuclei — as of 2026-04-29. That is an absence of evidence in those feeds, not a guarantee that the vulnerability is unexploited.

Affected products and versions

How to fix CVE-2025-39391

No vendor patch reference has been recorded for CVE-2025-39391 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2025-39391

1 tracked threat in the Threadlinqs corpus references CVE-2025-39391, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Enriched from CVE.org, NVD, FIRST EPSS. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.

Vulnerability database entry

Full detection coverage & IOCs for threats exploiting CVE-2025-39391 are available via the Threadlinqs MCP server (Purple tier). View plans →

← all vulnerabilities · Markdown version · Threadlinqs Intelligence