Unauthenticated commission settings disclosure via store-categories endpoint
Published Aug 21, 2026 · Updated Aug 21, 2026
Information disclosure in weDevs Dokan before 5.0.14 allows remote attackers to read vendor commission settings through a store REST endpoint. The endpoint serializes admin_commission_type and commission fields into anonymous responses instead of removing them as the single-store endpoint does. A vendor must have a published product in a category; category-based configuration exposes per-category and default rates, while every configuration exposes its commission type.
Summary
What happened
Information disclosure in weDevs Dokan before 5.0.14 allows remote attackers to read vendor commission settings through a store REST endpoint. The endpoint serializes admin_commission_type and commission fields into anonymous responses instead of removing them as the single-store endpoint does. A vendor must have a published product in a category; category-based configuration exposes per-category and default rates, while every configuration exposes its commission type.
The record
- CVE
- CVE-2026-16575
- Published
- Aug 21, 2026
- Updated
- Aug 21, 2026
- Vendor
- HappyMonster
- Product
- Dokan
- Classifications
- CWE-200
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 21, 2026CVE publishedPublication date reported by the CVE source.
- Aug 21, 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=0 <5.0.14
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.
Weakness, pattern, technique
Public exploit references
- Unauthenticated store-categories REST proof of conceptfunctional · demonstrated
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