CVE-2025-12809

dokan pro <= 4.1.3 - Missing Authorization to Unauthenticated Sensitive Information Exposure

2025-12-15 16:39
Ahmed Rayen Ayari

Strategic Overview

Status
Patched in 4.2.0
Affected Plugin
Dokan Pro
Affected Version
<= 4.1.3
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-12809
View all Dokan Pro vulnerabilities

At a glance

CVE-2025-12809 is a medium-severity Missing Authorization vulnerability in the Dokan Pro WordPress plugin, affecting versions <= 4.1.3. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.2.0; sites on affected versions should update now. Disclosed December 2025, reported by Ahmed Rayen Ayari.

Vulnerability Overview

The Dokan Pro plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the `/dokan/v1/wholesale/register` REST API endpoint in all versions up to, and including, 4.1.3. This makes it possible for unauthenticated attackers to enumerate users and retrieve their email addresses via the REST API by providing a user ID, along with other information such as usernames, display names, user roles, and registration dates.

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

Reaching this weakness in Dokan Pro <= 4.1.3 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 Dokan Pro the fix is 4.2.0: builds <= 4.1.3 are affected, anything from 4.2.0 onward is not.

Remediation

Update to version 4.2.0, 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: Dokan Pro 4.2.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-12809https://www.wordfence.com/threat-intel/vulnerabilities/id/534557b0-16d2-4a77-a118-b66fc7474ecfhttps://nvd.nist.gov/vuln/detail/CVE-2025-12809

Related records

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