LiveActive security incident?Get immediate response
CVE Record

CVE-2020-36717: Kali Forms <= 2.1.1 - Cross-Site Request Forgery

The Kali Forms plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.1.1. This is due to incorrect nonce handling throughout the plugin's function. This makes it possible for unauthenticated attackers to access the plugin's administrative functions via forged request granted they can trick a site administrator into performing an action such as clicking on a link.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-36717 affects the WordPress Kali Forms plugin through version 2.1.1. A malicious site or link could cause a logged-in administrator to trigger plugin administrative actions unintentionally. The issue is high severity because successful abuse could affect confidentiality, integrity, and availability of the site.

Executive priority

Treat this as a high-priority WordPress plugin remediation item if Kali Forms is present. It needs administrator interaction, but successful abuse could let an external attacker misuse trusted admin privileges.

Technical view

The vulnerability is CWE-352 cross-site request forgery caused by incorrect nonce handling across Kali Forms functions. The CVSS 3.1 score is 8.8 with network access, low complexity, no attacker privileges, and required administrator interaction. The source bundle does not provide request-level details.

Likely exposure

Exposure is likely limited to WordPress sites running Kali Forms versions up to and including 2.1.1, especially where administrators browse while authenticated. The affected metadata in the bundle is sparse, so confirm installed plugin versions directly.

Exploitation context

No CISA KEV listing is provided, and the bundle does not cite active exploitation. Practical abuse requires tricking a logged-in site administrator into performing an action, such as clicking a malicious link.

Researcher notes

Sources attribute the issue to incorrect nonce handling throughout plugin functions. The bundle does not include proof-of-concept details, a fixed version number, or confirmed exploitation evidence. Avoid assuming broader WordPress impact beyond Kali Forms.

Mitigation direction

  • Inventory WordPress sites for the Kali Forms plugin and installed version.
  • Update Kali Forms to a vendor-fixed or current release where available.
  • If updating is not possible, disable or remove the plugin until vendor guidance is applied.
  • Limit WordPress administrator sessions and privileges to reduce CSRF impact.
  • Review vendor advisories before applying production changes.

Validation and detection

  • Confirm whether any WordPress site runs Kali Forms version 2.1.1 or older.
  • Check vulnerability scanner results for CVE-2020-36717 on WordPress assets.
  • Review administrative audit logs for unexpected Kali Forms configuration or content changes.
  • Verify the plugin has been updated, disabled, or removed after remediation.
  • Document affected sites, remediation status, and any residual exception.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
cve · low confidence lookup

CVE-2020-36717 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2020-36717Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
wpchillKali Forms — Contact Form & Drag-and-Drop Builder0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

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.