CVE-2025-12809
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Dokan Pro plugin for WordPress has a broken access control vulnerability in the /dokan/v1/wholesale/register REST API endpoint. This endpoint lacks proper capability checks, allowing unauthenticated attackers to enumerate user data including email addresses, usernames, display names, user roles, and registration dates by supplying a user ID.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Dokan Pro is installedIn WordPress admin, go to Plugins and confirm Dokan Pro is active, or check the file system for the plugin files in /wp-content/plugins/dokan-pro/Affected if Dokan Pro plugin is installed and active
-
Identify Dokan Pro versionCheck the plugin header in dokan-pro.php or view the installed version number in the WordPress plugins admin pageAffected if The installed version matches or falls within the affected version range of Dokan Pro (check vendor advisories for specific versions)
-
Confirm REST API endpoint existsSend a GET or POST request to /wp-json/dokan/v1/wholesale/register without authentication headersAffected if The endpoint responds with HTTP 200 and returns data without requiring authentication
-
Test for unauthenticated user enumerationSend requests to the /dokan/v1/wholesale/register endpoint with various user ID parameters (e.g., ?user_id=1, ?user_id=2) without being logged inAffected if The endpoint returns user data such as email addresses, usernames, display names, roles, or registration dates without authentication
A user is affected if Dokan Pro is installed and the wholesale/register REST API endpoint is accessible without authentication, allowing enumeration of user data by supplying user IDs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper capability checks on the affected REST API endpoint to ensure only authorized users (e.g., administrators) can access user enumeration functionality. Consider upgrading to a patched version if available.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12809 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-12809 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data