CVE-2025-12416
BaseFortify
Publication date: 2025-11-04
Last updated on: 2025-11-04
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordpress | pagerank_tools | 1.1.5 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-352 | The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Stored Cross-Site Scripting (XSS) issue in the Pagerank Tools plugin for WordPress, affecting all versions up to 1.1.5. It occurs because the plugin's pr_save_settings() function lacks nonce validation and proper input sanitization. An attacker can exploit this by tricking a site administrator into clicking a malicious link (Cross-Site Request Forgery), causing malicious scripts to be stored and executed whenever the plugin's settings page is accessed.
How can this vulnerability impact me? :
This vulnerability can allow an unauthenticated attacker to inject malicious scripts into the plugin's settings page, which will execute in the context of the site when accessed by users. This can lead to theft of sensitive information, session hijacking, or other malicious actions performed on behalf of the administrator or users, potentially compromising the security and integrity of the website.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, immediately update the Pagerank Tools plugin for WordPress to a version later than 1.1.5 where the issue is fixed. If an update is not available, restrict access to the plugin's settings page to trusted administrators only and avoid clicking on suspicious links that could trigger the exploit. Additionally, monitor and validate all incoming requests to ensure nonce validation is properly implemented to prevent CSRF attacks.