Security Resilience

CVE-2025-39399

Published
24 April 2025
Modified
17 June 2026
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0075 54th percentile
Risk Priority 59 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-39399 is a high-severity PHP Remote File Inclusion (CWE-98) vulnerability. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 46% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

The vulnerability is a PHP Local File Inclusion issue stemming from improper control of filenames in include/require statements, tracked as CWE-98. It affects the License For Envato WordPress plugin by Ashraful Sarkar Naiem, with all versions through 1.0.0 impacted. The flaw carries a CVSS 3.1 score of 7.5.

Remote attackers can exploit the issue over the network without authentication, though high attack complexity and user interaction are required. Successful exploitation can yield high impact on confidentiality, integrity, and availability by allowing an attacker to include arbitrary local files within the PHP application.

The Patchstack advisory at the referenced URL documents the vulnerability in the wordpress-license-envato plugin and serves as the primary source for further details on affected code paths.

EPSS for the CVE rose from a low baseline to a peak of 0.0217 on 2026-06-02 before receding to the current value of 0.0046, indicating a post-disclosure increase in exploitation interest.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Ashraful Sarkar Naiem License For Envato license-envato allows PHP Local File Inclusion.This issue affects License For Envato: from n/a through <= 1.0.0.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-52807Shared CWE-98
CVE-2025-64360Shared CWE-98
CVE-2025-58215Shared CWE-98
CVE-2026-27988Shared CWE-98
CVE-2025-52728Shared CWE-98
CVE-2026-28096Shared CWE-98
CVE-2025-60194Shared CWE-98
CVE-2026-0926Shared CWE-98
CVE-2026-92174Shared CWE-98
CVE-2026-22442Shared CWE-98

Affected Assets

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and static analysis can discover missing filename restrictions before deployment.

Validating all inputs before they reach include/require statements directly stops untrusted filenames from being used.

Enforcing access authorizations on resources limits what an included file can reach even if a bad name is supplied.

Information-flow rules can block the loading of external or unauthorized files into the PHP process.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices such as input validation and allow-listing of include paths directly prevent the weakness.

PR.PS-01 partial match
blocks

Hardened runtime configuration (e.g., allow_url_include=off) directly blocks RFI even if code is flawed.

PR.PS-05 partial match
blocks

Execution restrictions can prevent the remote payload from running, while eliminating the weakness reduces the need for such controls.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect RFI but does not prevent the weakness by itself.

prevents

Secure coding standards directly require whitelisting and sanitization of filenames used in include/require statements.

References