CVE-2025-12641

Awesome Support – WordPress HelpDesk & Support Plugin <= 6.3.6 - Missing Authorization to Unauthenticated Role Demotion

2026-01-15 15:56
shark3y

Strategic Overview

Status
Patched in 6.3.7
Affected Version
<= 6.3.6
CVSS
6.5Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-12641
View all Awesome Support – WordPress HelpDesk & Support Plugin vulnerabilities

At a glance

CVE-2025-12641 is a medium-severity Missing Authorization vulnerability in the Awesome Support WordPress plugin, affecting versions <= 6.3.6. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.3.7; sites on affected versions should update now. Disclosed January 2026, reported by shark3y.

Vulnerability Overview

The Awesome Support - WordPress HelpDesk & Support Plugin for WordPress is vulnerable to authorization bypass due to missing capability checks in all versions up to, and including, 6.3.6. This is due to the 'wpas_do_mr_activate_user' function not verifying that a user has permission to modify other users' roles, combined with a nonce reuse vulnerability where public registration nonces are valid for privileged actions because all actions share the same nonce namespace. This makes it possible for unauthenticated attackers to demote administrators to low-privilege roles via the 'wpas-do=mr_activate_user' action with a user-controlled 'user_id' parameter, granted they can access the publicly available registration/submit ticket page to extract a valid nonce.

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, and no interaction from a victim user.

CWE-862: Missing Authorization

Awesome Support <= 6.3.6 carries this weakness at wpas_do_mr_activate_user, and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Awesome Support the fix is 6.3.7: builds <= 6.3.6 are affected, anything from 6.3.7 onward is not.

Remediation

Update to version 6.3.7, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Awesome Support 6.3.7 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C