# CVE-2025-12416: Pagerank Tools <= 1.1.5 - Cross-Site Request Forgery to Stored Cross-Site Scripting

> Attackers can trick admins into executing malicious scripts via CSRF, leading to stored XSS and potential account takeover in Pagerank Tools.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Nov 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-c9cf-gx4r-55f7

## What is CVE-2025-12416?

CVE-2025-12416 is a medium-severity vulnerability in mahype Pagerank tools, published on 4 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2025-12416?


## How do I fix CVE-2025-12416?

No fix has been published for CVE-2025-12416 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-12416 being exploited?

There is no known exploitation of CVE-2025-12416 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12416 and fix it if it is affected.

What it is: CVE-2025-12416 is a medium-severity vulnerability in mahype Pagerank tools, published on 4 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-12416 in the wild and no public exploit code.

Affected product: mahype Pagerank tools. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-12416/ (Markdown: https://insights.sbomify.com/CVE-2025-12416/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-12416
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-12416
- OSV: https://osv.dev/vulnerability/CVE-2025-12416

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-12416/
Summaries are generated and may contain mistakes; the official description above is the record.