# CVE-2025-12028: IndieAuth <= 4.5.4 - Cross-Site Request Forgery to Account Takeover via Stolen OAuth Tokens

> Attackers can force logged-in users to approve OAuth requests, stealing tokens to take over accounts via CSRF in the IndieAuth plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 24 Oct 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-43mm-w7h4-j7r2

## What is CVE-2025-12028?

CVE-2025-12028 is a high-severity vulnerability in indieweb IndieAuth, published on 24 Oct 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 IndieAuth plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.5.4. This is due to missing nonce verification on the `login_form_indieauth()` function and the authorization endpoint at wp-login.php?action=indieauth. This makes it possible for unauthenticated attackers to force authenticated users to approve OAuth authorization requests for attacker-controlled applications via a forged request granted they can trick a user into performing an action such as clicking on a link or visiting a malicious page while logged in. The attacker can then exchange the stolen authorization code for an access token, effectively taking over the victim's account with the granted scopes (create, update, delete).

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

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


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

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

## Is CVE-2025-12028 being exploited?

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

Public exploit code:

- https://github.com/jFriedli/CVE-2025-12028 (github_poc): https://github.com/jFriedli/CVE-2025-12028

## Fix prompt for AI coding agents

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

What it is: CVE-2025-12028 is a high-severity vulnerability in indieweb IndieAuth, published on 24 Oct 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-12028 in the wild and no public exploit code.

Affected product: indieweb IndieAuth. 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-12028/ (Markdown: https://insights.sbomify.com/CVE-2025-12028/index.md)
```

## Sources

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

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