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-12851: CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in wphocus My auctions allegro

0
High
VulnerabilityCVE-2025-12851cvecve-2025-12851cwe-98
Published: Fri Dec 05 2025 (12/05/2025, 09:27:00 UTC)
Source: CVE Database V5
Vendor/Project: wphocus
Product: My auctions allegro

Description

CVE-2025-12851 is a high-severity Local File Inclusion (LFI) vulnerability in the 'My auctions allegro' WordPress plugin by wphocus, affecting all versions up to 3. 6. 32. It allows unauthenticated attackers to manipulate the 'controller' parameter to include and execute arbitrary files on the server, potentially leading to remote code execution. This vulnerability can bypass access controls, expose sensitive data, and execute malicious PHP code, even when only 'safe' file types like images are uploaded. No known exploits are currently reported in the wild. The vulnerability has a CVSS score of 8. 1, indicating a significant risk. European organizations using this plugin on WordPress sites are at risk, especially those with public-facing auction or e-commerce platforms. Mitigation requires immediate patching or disabling the plugin, strict input validation, and restricting file upload types and locations.

AI-Powered Analysis

AILast updated: 12/05/2025, 10:00:49 UTC

Technical Analysis

CVE-2025-12851 is a Local File Inclusion vulnerability classified under CWE-98, found in the 'My auctions allegro' WordPress plugin developed by wphocus. The flaw exists in all versions up to and including 3.6.32 and is triggered via the 'controller' parameter. An attacker can exploit this vulnerability without authentication by manipulating this parameter to include arbitrary files from the server. This can lead to the execution of arbitrary PHP code embedded in those files, effectively enabling remote code execution. The vulnerability arises due to improper control over the filename used in include/require statements, allowing attackers to bypass intended access controls. This can result in unauthorized data disclosure, code execution, and full compromise of the affected web server. The vulnerability is rated high severity with a CVSS 3.1 score of 8.1, reflecting network attack vector, high impact on confidentiality, integrity, and availability, and no user interaction required. Although no public exploits are currently known, the nature of the vulnerability makes it a critical risk for WordPress sites using this plugin, especially those handling auctions or e-commerce functions. The lack of available patches necessitates immediate mitigation efforts by administrators.

Potential Impact

For European organizations, this vulnerability poses a significant threat to the confidentiality, integrity, and availability of web servers running WordPress with the vulnerable plugin. Exploitation can lead to unauthorized access to sensitive customer data, including auction details and user credentials, potentially violating GDPR and other data protection regulations. The ability to execute arbitrary PHP code can allow attackers to deploy web shells, pivot within internal networks, and disrupt business operations. E-commerce platforms and auction sites are particularly at risk due to their public exposure and transactional nature. The reputational damage and potential financial losses from data breaches or service outages could be substantial. Additionally, the vulnerability could be leveraged in broader cyber campaigns targeting European digital marketplaces, increasing the risk for organizations in countries with high e-commerce activity.

Mitigation Recommendations

1. Immediately disable or uninstall the 'My auctions allegro' plugin until a secure patch is released. 2. Monitor official vendor channels and WordPress plugin repositories for updates or patches addressing CVE-2025-12851. 3. Implement strict input validation and sanitization on the 'controller' parameter to prevent malicious file inclusion. 4. Restrict file upload types and enforce server-side checks to prevent uploading executable PHP code disguised as images or other safe file types. 5. Use web application firewalls (WAFs) with custom rules to detect and block suspicious requests targeting the 'controller' parameter. 6. Conduct regular security audits and vulnerability scans focusing on WordPress plugins and their configurations. 7. Employ the principle of least privilege on web server file permissions to limit the impact of any successful exploitation. 8. Maintain comprehensive logging and monitoring to detect anomalous file inclusion attempts or code execution activities. 9. Educate site administrators about the risks of using outdated or unmaintained plugins and encourage timely updates.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-06T23:45:33.325Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6932a9b1f88dbe026c8e9fb0

Added to database: 12/5/2025, 9:45:21 AM

Last enriched: 12/5/2025, 10:00:49 AM

Last updated: 12/5/2025, 12:06:23 PM

Views: 4

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