Authenticated vendor payout hijacking via unchecked vendor ID
Published Jan 20, 2026 · Updated Jan 20, 2026
Improper access control in Dokan 4.2.4 and earlier allows remote authenticated users to read or modify other vendors' store settings. The /wp-json/dokan/v1/settings endpoint uses a user-controlled vendor_id to fetch or update a vendor without verifying that the requester can access that store. Customer-level access is sufficient to disclose banking and contact data or replace a vendor's PayPal email, redirecting later marketplace payouts.
Summary
What happened
Improper access control in Dokan 4.2.4 and earlier allows remote authenticated users to read or modify other vendors' store settings. The /wp-json/dokan/v1/settings endpoint uses a user-controlled vendor_id to fetch or update a vendor without verifying that the requester can access that store. Customer-level access is sufficient to disclose banking and contact data or replace a vendor's PayPal email, redirecting later marketplace payouts.
The record
- CVE
- CVE-2025-14977
- Published
- Jan 20, 2026
- Updated
- Jan 20, 2026
- Vendor
- Dokan Inc.
- Product
- Dokan
- Classifications
- CWE-284, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 20, 2026CVE publishedPublication date reported by the CVE source.
- Jan 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=* <=4.2.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Atomic Edge PHP proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo