dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2025-14977

HIGH · 8.1 CVSS v3.1 Published 2026-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
The Dokan: AI Powered WooCommerce Multivendor Marketplace Solution – Build Your Own Amazon, eBay, Etsy plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 4.2.4 via the `/wp-json/dokan/v1/settings` REST API endpoint due to missing validation on a user-controlled key. This makes it possible for authenticated attackers, with customer-level permissions and above, to read or modify other vendors' store settings including sensitive payment information (PayPal email, bank account details, routing numbers, IBAN, SWIFT codes), phone numbers, and addresses, and change PayPal email addresses to attacker-controlled addresses, enabling financial theft when the marketplace processes payouts.

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 confidence

The Dokan plugin for WordPress versions up to 4.2.4 contains an Insecure Direct Object Reference vulnerability in the `/wp-json/dokan/v1/settings` REST API endpoint. The endpoint fails to validate that the authenticated user has authorization to access or modify specific vendor settings, allowing any authenticated user with customer-level permissions to read or modify other vendors' sensitive payment information including PayPal emails, bank account details, routing numbers, IBAN, and SWIFT codes.

MitigationRestrict access by implementing proper authorization checks in the REST API endpoint to verify the requesting user owns or has permission to modify the specific vendor settings being accessed, and validate user capabilities before returning or accepting any sensitive payment data.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Dokan plugin version
    Navigate to WordPress admin > Plugins and locate Dokan, or inspect the plugin file header at /wp-content/plugins/dokan/includes/class-plugin.php or check the version defined in the main plugin file
    Affected if The installed version is lower than 4.2.5 (the fixed release)
  2. Confirm REST API endpoint accessibility
    Send a GET request to /wp-json/dokan/v1/settings with a low-privilege user session (customer role or above) and observe if the endpoint responds
    Affected if The endpoint returns a successful response for non-administrator users, indicating the vulnerability is exposed
  3. Check for vendor ID parameter handling
    Submit a request to /wp-json/dokan/v1/settings with a modified vendor_id parameter referencing a different vendor than the authenticated user, and check if the API returns that vendor's settings
    Affected if The API returns settings for a vendor other than the one associated with the authenticated user, confirming the IDOR is present
  4. Review user role configuration
    Inspect the WordPress user roles assigned to test accounts, verifying that customer-level or higher roles can access the Dokan REST API endpoints
    Affected if Customer, vendor, or other non-administrator roles have REST API access to the /wp-json/dokan/v1/settings endpoint

You are affected if the Dokan plugin version is below 4.2.5 and the REST API endpoint /wp-json/dokan/v1/settings is accessible to non-administrator users without proper vendor ID authorization checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict access by implementing proper authorization checks in the REST API endpoint to verify the requesting user owns or has permission to modify the specific vendor settings being accessed, and validate user capabilities before returning or accepting any sensitive payment data.

Recommended fix Moderate confidence

Latest version after 4.2.4 (check wordpress.org for current stable release)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Dokan plugin in the list
  4. Click 'Update now' if an update is available, or manually upload the latest version from wordpress.org
  5. Verify the update completes successfully
  6. Test that the `/wp-json/dokan/v1/settings` endpoint now properly validates user permissions

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14977 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14977 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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