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-12416: CWE-352 Cross-Site Request Forgery (CSRF) in mahype Pagerank tools

0
Medium
VulnerabilityCVE-2025-12416cvecve-2025-12416cwe-352
Published: Tue Nov 04 2025 (11/04/2025, 04:27:13 UTC)
Source: CVE Database V5
Vendor/Project: mahype
Product: Pagerank tools

Description

The Pagerank Tools plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Cross-Site Request Forgery in all versions up to, and including, 1.1.5. This is due to missing nonce validation on the pr_save_settings() function and insufficient input sanitization. This makes it possible for unauthenticated attackers to inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. The injected scripts will execute whenever a user accesses the plugin's settings page.

AI-Powered Analysis

AILast updated: 11/11/2025, 08:20:24 UTC

Technical Analysis

The mahype Pagerank Tools plugin for WordPress, up to and including version 1.1.5, contains a vulnerability identified as CVE-2025-12416, categorized under CWE-352 (Cross-Site Request Forgery). The vulnerability stems from the pr_save_settings() function lacking nonce validation, a security mechanism designed to verify the legitimacy of requests. Additionally, the plugin fails to sufficiently sanitize user inputs before storing them. This combination allows an attacker to craft a malicious request that, when an authenticated administrator is tricked into clicking (via social engineering or phishing), results in the injection of malicious JavaScript code stored persistently within the plugin’s settings. When any user subsequently visits the plugin’s settings page, the malicious script executes in their browser context, potentially leading to session hijacking, privilege escalation, or data theft. The vulnerability requires no prior authentication (PR:N) but does require user interaction (UI:R) in the form of the administrator clicking a malicious link. The CVSS v3.1 base score is 6.1, reflecting a medium severity with network attack vector, low attack complexity, and impact on confidentiality and integrity but no impact on availability. No patches or exploits are currently publicly available, but the risk remains significant due to the stored XSS nature and the potential for widespread impact if exploited in administrative contexts.

Potential Impact

For European organizations, especially those relying on WordPress for content management and using the mahype Pagerank Tools plugin, this vulnerability poses a risk of unauthorized script execution within administrative interfaces. This can lead to theft of administrative credentials, unauthorized changes to site configurations, and potential lateral movement within the organization’s web infrastructure. The impact on confidentiality and integrity is notable, as attackers can hijack sessions or inject further malicious payloads. Given the widespread use of WordPress across European SMEs, government portals, and enterprises, exploitation could disrupt business operations and damage reputations. The absence of known exploits currently limits immediate risk, but the ease of exploitation via social engineering and the stored nature of the XSS make it a persistent threat. Organizations with less mature patch management or limited security awareness training for administrators are particularly vulnerable.

Mitigation Recommendations

Immediate mitigation involves disabling or removing the mahype Pagerank Tools plugin until a security patch is released. Administrators should monitor official mahype channels for updates addressing nonce validation and input sanitization. In the interim, organizations can implement Web Application Firewall (WAF) rules to detect and block suspicious POST requests targeting the pr_save_settings() endpoint. Security teams should enforce strict administrator training to recognize phishing attempts and avoid clicking untrusted links. Reviewing and restricting administrative access to trusted personnel reduces exposure. Additionally, applying Content Security Policy (CSP) headers can help mitigate the impact of injected scripts. For organizations with development capabilities, manually patching the plugin to add nonce verification and sanitize inputs before saving settings is advisable. Regular security audits and vulnerability scanning of WordPress plugins should be intensified to detect similar issues proactively.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-10-28T15:45:10.914Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 690984df2b77ca42b4883f4c

Added to database: 11/4/2025, 4:45:19 AM

Last enriched: 11/11/2025, 8:20:24 AM

Last updated: 12/19/2025, 3:29:17 PM

Views: 74

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