CVE-2026-107774: Dokan < 5.3.3 - Unauthenticated Email Sender Spoofing via Store Contact Form
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Unknown Dokan: AI Powered WooCommerce Multivendor Marketplace Solution 5.3.3.
Low priority for now. Upgrade to Unknown Dokan: AI Powered WooCommerce Multivendor Marketplace Solution 5.3.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The Dokan: AI Powered WooCommerce Multivendor Marketplace Solution WordPress plugin before 5.3.3 does not use a trusted site-owned sender address when relaying its store contact form, instead placing the unauthenticated submitter's supplied address directly in the message's From header rather than a Reply-To, allowing unauthenticated attackers to make the site email its own vendors with the sender spoofed to an address at the site's own domain (such as its administrator), aligned with the domain's own SPF/DKIM.
- Published
- Nov 5, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-290
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Is Dokan: AI Powered WooCommerce Multivendor Marketplace Solution – Build Your Own Amazon, eBay, Etsy on your site?
WP Lens reads your site's plugin, theme and WordPress versions from the outside and matches them to known vulnerabilities. Works without an account.
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (WPScan). Independent of NVD's CPE analysis and usually ahead of it.
Unknown Dokan: AI Powered WooCommerce Multivendor Marketplace Solution
- before 5.3.3affected · semver
Same product
unknown: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-16576Dokan < 5.0.14 - Shop Manager+ Arbitrary Plugin Installation/Activation via REST API28Monitor
- CVE-2026-107773Dokan < 5.3.3 - Unauthenticated Order PII Disclosure and Note Manipulation via Orders REST Endpoint26Monitor
- CVE-2026-16575Dokan < 5.0.14 - Unauthenticated Commission Settings Disclosure via Store Categories REST Endpoint21Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-16577Aug 21, 2026 · Dokan < 5.0.14 - Vendor+ Reverse Withdrawal Ledger Manipulation via Client-Supplied Amount10Monitor
- ← EarlierCVE-2026-107694Oct 11, 2026 · Dokan < 5.2.0 - Vendor+ Cross-Vendor Commission Settings Disclosure via Commission REST Endpoint10Monitor
- Later →CVE-2026-107775Nov 5, 2026 · Dokan < 5.3.3 - Admin+ Cross-Site Vendor Activation10Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Unknown Dokan: AI Powered WooCommerce Multivendor Marketplace Solution | 5.3.3 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 11, 2026+6 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Abdullah Kareem "cyberkareem"finder
- WPScancoordinator
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-290 · Authentication Bypass by SpoofingCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Exploitation of Trusted IdentifiersCAPEC-21likelihood: High · High
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Creating a Rogue Certification Authority CertificateCAPEC-459likelihood: Medium · Very High
- Web Services API Signature Forgery Leveraging Hash Function Extension WeaknessCAPEC-461High
- Signature SpoofCAPEC-473
- Signature Spoofing by MisrepresentationCAPEC-476likelihood: Low · High
- Session Credential Falsification through PredictionCAPEC-59likelihood: High · High
- Reusing Session IDs (aka Session Replay)CAPEC-60likelihood: High · High
ATT&CK techniques
- Masquerading: Invalid Code SignatureT1036.001
- Access Token ManipulationT1134
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Steal Application Access TokenT1528
- Steal Web Session CookieT1539
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Subvert Trust Controls: Code SigningT1553.002
- Adversary-in-the-MiddleT1557
Change log
- CVSS— → 5.3
- Severity— → medium
- SSVC exploitation— → none
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.