Security readout for executives and security teams
Plain-English summary
A vulnerable WordPress KingComposer plugin version could let a logged-in Author or higher upload files the server may execute. That can turn a content-author account compromise into full website compromise. The issue is serious for public WordPress sites using KingComposer 2.9.3 or earlier.
Executive priority
Treat as a high-priority WordPress remediation where KingComposer is deployed, especially on sites with many content users or external contributors. Prioritize patching and account review before routine backlog work.
Technical view
CVE-2020-36701 is a CWE-434 arbitrary file upload in KingComposer through 2.9.3, reportedly in process_bulk_action within kingcomposer/includes/kc.extensions.php. It requires authenticated Author-level privileges or higher, has low attack complexity, and carries high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to WordPress sites with Page Builder: KingComposer installed at versions up to 2.9.3 and reachable by Author-level users or compromised Author accounts.
Exploitation context
The source bundle does not identify CISA KEV listing or confirmed active exploitation. The risk is still material because Author-level access is common on content-heavy WordPress sites and successful abuse may enable server-side code execution.
Researcher notes
The bundle identifies the vulnerable component and function path, but the affected metadata is sparse and partly inconsistent. Base analysis on the title, description, CVSS vector, Wordfence, Nintechnet, WordPress plugin, and Trac references rather than expanding scope beyond KingComposer.
Mitigation direction
- Update KingComposer to version 2.9.4 or later where available.
- Remove or disable KingComposer if it is unused.
- Restrict Author-level access until affected sites are updated.
- Review vendor and WordPress plugin guidance for current supported versions.
- Check uploaded files and webroot paths for unexpected executable content.
Validation and detection
- Inventory WordPress sites for active KingComposer installations.
- Confirm the installed plugin version is not 2.9.3 or earlier.
- Review Author and higher-privileged accounts for unnecessary access.
- Inspect web server and WordPress logs for suspicious upload activity.
- Verify remediation through plugin version records or WordPress admin evidence.
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-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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 lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-36701 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
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/45a62dd0-386c-41b3-b8dd-ced443da9f92?source=cveCVE reference
- https://blog.nintechnet.com/wordpress-kingcomposer-page-builder-fixed-multiple-critical-vulnerabilities/CVE reference
- https://wordpress.org/plugins/kingcomposer/#developersCVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=2320014%40kingcomposer&new=2320014%40kingcomposer&sfp_email=&sfph_mail=CVE 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.
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.