Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-12497: CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in averta Premium Portfolio Features for Phlox theme

0
High
VulnerabilityCVE-2025-12497cvecve-2025-12497cwe-98
Published: Wed Nov 05 2025 (11/05/2025, 11:24:40 UTC)
Source: CVE Database V5
Vendor/Project: averta
Product: Premium Portfolio Features for Phlox theme

Description

The Premium Portfolio Features for Phlox theme plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.3.10 via the 'args[extra_template_path]' parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included.

AI-Powered Analysis

AILast updated: 11/12/2025, 11:56:52 UTC

Technical Analysis

CVE-2025-12497 is a Local File Inclusion vulnerability classified under CWE-98, found in the Premium Portfolio Features for Phlox theme plugin for WordPress, versions up to and including 2.3.10. The vulnerability arises from improper validation and control of the 'args[extra_template_path]' parameter, which is used in PHP include or require statements. An attacker can manipulate this parameter to include arbitrary PHP files from the server, leading to remote code execution (RCE). This can be exploited without any authentication or user interaction, although the attack complexity is rated high due to the need to identify or upload suitable PHP files. Successful exploitation allows attackers to bypass access controls, execute arbitrary code, and potentially access sensitive data stored on the server. The vulnerability affects all versions of the plugin, and no patches or updates have been published at the time of disclosure. The CVSS 3.1 base score is 8.1, reflecting high confidentiality, integrity, and availability impacts. The vulnerability is particularly dangerous in environments where attackers can upload PHP files (e.g., via other vulnerabilities or misconfigurations), as these files can then be included and executed by the vulnerable plugin. Although no known exploits are currently reported in the wild, the risk remains significant due to the widespread use of WordPress and the Phlox theme in various websites.

Potential Impact

For European organizations, this vulnerability poses a serious threat to the confidentiality, integrity, and availability of web servers running WordPress sites with the affected Phlox theme plugin. Exploitation can lead to full server compromise, data breaches involving sensitive customer or business information, defacement of websites, or use of compromised servers as pivot points for further attacks within corporate networks. Organizations in sectors such as e-commerce, finance, healthcare, and government are particularly at risk due to the sensitive nature of their data and regulatory requirements like GDPR. The ability for unauthenticated attackers to execute arbitrary PHP code increases the likelihood of automated exploitation attempts. Additionally, compromised websites can be used to distribute malware or conduct phishing campaigns, amplifying the impact beyond the initial target. The lack of available patches increases the urgency for organizations to implement alternative mitigations promptly.

Mitigation Recommendations

1. Immediately audit all WordPress installations for the presence of the Premium Portfolio Features for Phlox theme plugin and verify the version. 2. If possible, upgrade to a patched version once released by the vendor; monitor vendor channels for updates. 3. In the absence of patches, disable or remove the vulnerable plugin to eliminate the attack surface. 4. Implement strict web application firewall (WAF) rules to block requests containing suspicious 'args[extra_template_path]' parameters or attempts to include files via URL parameters. 5. Restrict file upload capabilities on the server and enforce strict file type validation to prevent uploading of PHP files. 6. Harden PHP configurations by disabling dangerous functions (e.g., allow_url_include, allow_url_fopen) and restricting include paths. 7. Monitor web server logs for unusual access patterns or attempts to exploit the parameter. 8. Employ intrusion detection/prevention systems (IDS/IPS) tuned to detect LFI attempts. 9. Conduct regular security assessments and penetration testing focused on web application vulnerabilities. 10. Educate development and operations teams about secure coding practices to prevent similar vulnerabilities in custom themes or plugins.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-10-29T23:05:58.113Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 690b36fdeb4434bb4f87474d

Added to database: 11/5/2025, 11:37:33 AM

Last enriched: 11/12/2025, 11:56:52 AM

Last updated: 12/19/2025, 8:56:34 AM

Views: 102

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats