IndieAuth

IndieAuth has one disclosed vulnerability in the WordSec catalog, all reported in 2025; it is fixed as of September 2026. Their average CVSS score is 8.8, and the most serious one scores 8.8 out of 10. Severity breakdown: 0 critical and 1 high.

The most common weakness is Cross-Site Request Forgery (CSRF), behind 1 of the records (100%).

The one issue recorded for IndieAuth has a vendor fix available, so running the current release closes it.

All of these findings were reported by Jonas Benjamin Friedli. IndieAuth is installed on roughly 400 WordPress sites, so each unpatched flaw has a wide blast radius. The current release is tested up to WordPress 7.1.

Strategic Overview

Avg CVSSHigh

8.8/ 10

Patch Coverage100%

Open

Fixed

Get automatic notifications for all IndieAuth vulnerabilities before they are exploited.

Highest severity on recordCVSS 8.8CVE-2025-12028

IndieAuth <= 4.5.4 - Cross-Site Request Forgery to Account Takeover via Stolen OAuth Tokens

Read the full analysis

Vulnerability Records

1 records


2025-10-23 19:57	IndieAuth <= 4.5.4 - Cross-Site Request Forgery to Account Takeover via Stolen OAuth Tokens IndieAuth <= 4.5.4	`CVE-2025-12028`	8.8 High	Jonas Benjamin Friedli	Yes

Showing 1–1 of 1 reports

Latestv4.7.2

IndieAuth

Author

IndieWeb

5.0(4)

100/100

Last Updated

2026-08-31 (12d ago)

Active Installs

400+

Downloads

34,222

Requires WP

6.2+

Requires PHP

7.4+

Tested up to

WP 7.1

Created

2013-09-16 (13y ago)

The plugin turns WordPress into an IndieAuth endpoint. This can be used to act as an authentication mechanism for WordPress and its REST API, as well as an identity mechanism for other sites. It uses the URL from the profile page to identify the blog user or your author url. We recommend your site be served over https to use this. You can also install this plugin to enable web sign-in for your site using your domain.

View on WordPress.org