Security Resilience

CVE-2025-60065

Axiomthemes Pinevale ≤ 1.0.14

Published
18 December 2025
Modified
27 April 2026
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0050 42th percentile
Risk Priority 60 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-60065 is a high-severity PHP Remote File Inclusion (CWE-98) vulnerability in Axiomthemes Pinevale. Its CVSS base score is 8.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 42th percentile by exploit likelihood (below the median); 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.

CVE-2025-60065 is an Improper Control of Filename for Include/Require Statement in PHP Program vulnerability, classified under CWE-98 and labeled as a PHP Remote File Inclusion issue, which enables PHP Local File Inclusion in the Pinevale WordPress theme developed by axiomthemes. This flaw affects Pinevale versions from n/a through 1.0.14, as published on 2025-12-18.

The vulnerability carries a CVSS v3.1 base score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating exploitation is possible over the network by unauthenticated attackers with no user interaction required, albeit with high attack complexity. Successful exploitation allows attackers to achieve high impacts on confidentiality, integrity, and availability, typically through the inclusion and potential execution of arbitrary local files on the affected server.

Mitigation details are documented in the Patchstack advisory at https://patchstack.com/database/Wordpress/Theme/pinevale/vulnerability/wordpress-pinevale-theme-1-0-14-local-file-inclusion-vulnerability?_s_id=cve, which covers the Local File Inclusion vulnerability in the Pinevale WordPress theme version 1.0.14.

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 axiomthemes Pinevale pinevale allows PHP Local File Inclusion.This issue affects Pinevale: from n/a through <= 1.0.14.

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-58944Same vendor: Axiomthemes
CVE-2025-58927Same vendor: Axiomthemes
CVE-2025-58934Same vendor: Axiomthemes
CVE-2025-53442Same vendor: Axiomthemes
CVE-2025-58936Same vendor: Axiomthemes
CVE-2025-53448Same vendor: Axiomthemes
CVE-2025-58933Same vendor: Axiomthemes
CVE-2025-58941Same vendor: Axiomthemes
CVE-2025-53441Same vendor: Axiomthemes
CVE-2025-58926Same vendor: Axiomthemes

Affected Assets

axiomthemes
pinevale
≤ 1.0.14

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