LiveActive security incident?Get immediate response
CVE Record

CVE-2020-13485: The Knock Knock plugin before 1.2.8 for Craft CMS allows IP Whitelist bypass via an X-Forwarded-For HTTP he...

The Knock Knock plugin before 1.2.8 for Craft CMS allows IP Whitelist bypass via an X-Forwarded-For HTTP header.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue affects the Knock Knock plugin for Craft CMS before 1.2.8. A visitor could spoof the X-Forwarded-For header and bypass an IP whitelist. Business risk depends on whether the plugin protects private or pre-release site content.

Executive priority

Prioritize if Knock Knock protects confidential content, staging environments, or administrative workflows. Otherwise handle through normal dependency remediation, because active exploitation is not shown in the supplied sources.

Technical view

CVE-2020-13485 is an IP whitelist bypass in Knock Knock before 1.2.8 for Craft CMS. The reported bypass uses the X-Forwarded-For HTTP header. Sources do not provide CVSS, CWE, exploit maturity, or detailed affected deployment conditions.

Likely exposure

Exposure is likely limited to Craft CMS sites using Knock Knock before 1.2.8 with IP whitelisting enabled or relied upon for access restriction.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. The bug is conceptually easy to understand, but provided sources do not include exploit steps or exploitation prevalence.

Researcher notes

The available record is sparse: no CVSS, CWE, CPEs, or detailed exploit conditions are included. Validate against the plugin changelog, Limpid Security advisory, and local proxy topology before rating site-specific impact.

Mitigation direction

  • Inventory Craft CMS sites for the Knock Knock plugin.
  • Upgrade Knock Knock from versions before 1.2.8.
  • Review vendor changelog and advisory for supported remediation guidance.
  • Avoid relying on client-supplied forwarding headers for access decisions.
  • Add stronger authentication for restricted content where practical.

Validation and detection

  • Confirm installed Knock Knock plugin versions across Craft CMS deployments.
  • Verify whether IP whitelist functionality is enabled and security-relevant.
  • Review reverse proxy handling of X-Forwarded-For headers.
  • Check access logs for suspicious forwarded-header patterns.
  • Retest whitelist behavior after updating or reconfiguring.
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.

cve · low confidence lookup

CVE-2020-13485 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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