Dokan < 5.3.3 - Vendor+ Reverse Withdrawal Ledger Credit Without Payment via Discount Coupon
- Exploited
- No known exploitation
- Fix
- Fixed in 5.3.3
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 5.3.3.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.20% · 10th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 5/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Dokan WordPress plugin, used to run multi-vendor marketplaces, is affected by a flaw in how it credits a vendor's reverse-withdrawal ledger during checkout. A vendor with high privileges can reach it remotely over the network and, when a discount coupon is applied, clear part of their outstanding commission debt while paying less than they owe, which affects integrity.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
The Dokan WordPress plugin before 5.3.3 does not reconcile the amount credited to a vendor's reverse-withdrawal ledger against the amount actually collected for the payment order, allowing a vendor to clear their outstanding commission debt while paying less than the balance owed when a discount coupon is applied at checkout.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity2.2/10CVSS 2.2
- No patch0/5No signal
What would change the score
- Would score about 60 if added to CISA KEV
- Would score about 55 if CISA's SSVC rates exploitation active
- Would score about 24 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 5.3.3.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Unknown Dokan
fixed in 5.3.3
Evidence 1
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-107776
Is CVE-2026-107776 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-107776?
Dokan: before 5.3.3.Source: cve.now feed data
How do I fix CVE-2026-107776?
Upgrade to a fixed version: 5.3.3.Source: cve.now feed data