# CVE-2025-5931: Dokan Pro <= 4.0.5 - Authenticated (Vendor+) Privilege Escalation

> Authenticated vendors can escalate privileges and change arbitrary user passwords, including administrators, due to improper identity validation during staff password resets.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-mg63-9vwr-f2mv

## What is CVE-2025-5931?

CVE-2025-5931 is a high-severity vulnerability in wedevs Dokan Pro, published on 26 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Dokan Pro plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 4.0.5. This is due to the plugin not properly validating a user's identity prior to updating their password during a staff password reset. This makes it possible for authenticated attackers, with vendor-level access and above, to elevate their privilege to the level of a staff member and then change arbitrary user passwords, including those of administrators in order to gain access to their accounts. By default, the plugin allows customers to become vendors.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2025-5931?


## How do I fix CVE-2025-5931?

No fix has been published for CVE-2025-5931 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-5931 being exploited?

There is no known exploitation of CVE-2025-5931 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5931 and fix it if it is affected.

What it is: CVE-2025-5931 is a high-severity vulnerability in wedevs Dokan Pro, published on 26 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-5931 in the wild and no public exploit code.

Affected product: wedevs Dokan Pro. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-5931/ (Markdown: https://insights.sbomify.com/CVE-2025-5931/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-5931
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-5931
- OSV: https://osv.dev/vulnerability/CVE-2025-5931

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-5931/
Summaries are generated and may contain mistakes; the official description above is the record.