Asgaros Forum <= 3.2.1 - Cross-Site Request Forgery to Subscription Settings Update
Strategic Overview
- Status
- Patched in 3.3.0
- Affected Plugin
- Asgaros Forum
- Affected Version
<= 3.2.1- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2025-12901
At a glance
CVE-2025-12901 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Asgaros Forum WordPress plugin, affecting versions <= 3.2.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.3.0; sites on affected versions should update now. Disclosed November 2025, reported by Brian Mungai.
Vulnerability Overview
The Asgaros Forum plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.2.1. This is due to missing nonce validation on the set_subscription_level() function. This makes it possible for unauthenticated attackers to modify the subscription settings of authenticated users via a forged request granted they can trick a logged-in user into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Asgaros Forum <= 3.2.1 carries this weakness at set_subscription_level(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Asgaros Forum the fix is 3.3.0: builds <= 3.2.1 are affected, anything from 3.3.0 onward is not.
Remediation
Update to version 3.3.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Asgaros Forum: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Asgaros Forum 3.3.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Asgaros Forum
- 9.8CVE-2024-22284: Asgaros Forum PHP Object Injection
CVE-2024-22284 - 9.8CVE-2021-24827: Asgaros Forum <= 1.15.12 SQL Injection
CVE-2021-24827 - 8.8CVE-2022-0411: Asgaros Forum < 2.0.0 SQL Injection
CVE-2022-0411 - 7.5CVE-2025-11452: Asgaros Forum <= 3.1.0 SQL Injection
CVE-2025-11452 - 7.2CVE-2021-25045: Asgaros Forum <= 1.15.14 Admin+ SQL Injection
CVE-2021-25045 - 6.6CVE-2023-5604: Asgaros Forum Insufficient Authorization
CVE-2023-5604 - 6.4CVE-2025-39514: Asgaros Forum <= 3.2.1 Stored Cross-Site Scripting
CVE-2025-39514 - 4.8CVE-2021-42365: Asgaros Forums <= 1.15.13 Stored Cross-Site Scripting
CVE-2021-42365
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C