Security readout for executives and security teams
Plain-English summary
CVE-2020-36748 affects the Dokan WordPress marketplace plugin up to and including version 3.0.8. A malicious site could trick a logged-in administrator into triggering an order export because the export handler did not properly validate a nonce. Public sources rate this as medium severity, with no KEV listing or provided evidence of active exploitation.
Executive priority
Treat this as a moderate-priority WordPress plugin hygiene issue. It is not marked as actively exploited, but marketplace sites should update promptly because administrator-assisted actions can affect order-management workflows.
Technical view
The flaw is a CSRF issue in Dokan's handle_order_export() function caused by missing or incorrect nonce validation. Attackers need no account, but must induce an administrator action. The CVSS 3.1 score is 4.3, with low integrity impact and no stated confidentiality or availability impact.
Likely exposure
Exposure is likely limited to WordPress sites running Dokan versions up to 3.0.8, especially WooCommerce multivendor marketplaces where administrators remain logged in during routine browsing or email review.
Exploitation context
The source bundle describes user-assisted CSRF only. It requires an administrator to perform an attacker-influenced action such as clicking a link. KEV is false, and the provided sources do not establish active exploitation.
Researcher notes
Do not infer data theft from the word export; the provided CVSS vector states no confidentiality impact. The key validation question is whether order export actions reject forged requests without a valid nonce in affected versus fixed versions.
Mitigation direction
- Update Dokan from versions up to 3.0.8 to a vendor-supported fixed release.
- Confirm the installed Dokan version in WordPress plugin inventory.
- Review vendor and WordPress plugin guidance for the nonce validation fix.
- Train administrators to avoid unsolicited links while logged into WordPress.
- Use least-privilege admin accounts for marketplace operations.
Validation and detection
- Identify all WordPress sites with Dokan installed.
- Check whether any installation is version 3.0.8 or earlier.
- Review plugin changelogs or the referenced WordPress Trac changeset for the export fix.
- Confirm order export requests require valid nonce validation after updating.
- Check web logs for suspicious administrator-triggered order export requests.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2020-36748 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/894c875a-078f-4c1f-83d2-4a6e4a309c3e?source=cveCVE reference
- https://blog.nintechnet.com/25-wordpress-plugins-vulnerable-to-csrf-attacks/CVE reference
- https://blog.nintechnet.com/more-wordpress-plugins-and-themes-vulnerable-to-csrf-attacks/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-3/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-2/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-1/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-5/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-4/CVE reference
- https://plugins.trac.wordpress.org/changeset/2368433/dokan-lite/trunk/includes/Dashboard/Templates/Orders.phpCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.