CVE-2025-12028
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-10-24

Last updated on: 2026-04-08

Assigner: Wordfence

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).
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-10-24
Last Modified
2026-04-08
Generated
2026-05-06
AI Q&A
2025-10-24
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wordpress indieauth *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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 Cross-Site Request Forgery (CSRF) issue in the IndieAuth plugin for WordPress versions up to 4.5.4. It occurs because the plugin does not verify a security nonce in the login_form_indieauth() function and the authorization endpoint at wp-login.php?action=indieauth. This allows an attacker to trick an authenticated user into approving OAuth authorization requests for attacker-controlled applications by making the user perform an action like clicking a link or visiting a malicious page while logged in.


How can this vulnerability impact me? :

An attacker can exploit this vulnerability to force a logged-in user to approve OAuth authorization requests for malicious applications. The attacker can then exchange the stolen authorization code for an access token, effectively taking over the victim's account with permissions to create, update, and delete content or data within the scope granted.


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, immediately update the IndieAuth plugin for WordPress to a version later than 4.5.4 where the nonce verification issue is fixed. Additionally, avoid clicking on suspicious links or visiting untrusted pages while logged in to WordPress to reduce the risk of CSRF attacks.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart