LiveActive security incident?Get immediate response
CVE Record

CVE-2020-29477: Invision Community 4.5.4 is affected by cross-site scripting (XSS) in the Field Name field.

Invision Community 4.5.4 is affected by cross-site scripting (XSS) in the Field Name field. This vulnerability can allow an attacker to inject the XSS payload in Field Name and each time any user will open that, the XSS triggers and the attacker can able to steal the cookie according to the crafted payload.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-29477 is a stored cross-site scripting issue reported in Invision Community 4.5.4. An attacker who can place malicious content in a Field Name could cause script to run when another user views it, potentially exposing session cookies depending on browser and cookie protections.

Executive priority

Address during the next web-application security maintenance cycle unless the affected feature is internet-facing or broadly writable; then prioritize sooner due to session theft risk.

Technical view

The public description identifies XSS in the Field Name field of Invision Community 4.5.4. The record does not provide CVSS, CWE, fixed-version, or vendor mitigation data. Exploit-DB is listed as a public reference, but CISA KEV status is false in the provided bundle.

Likely exposure

Exposure appears limited to organizations running Invision Community 4.5.4 with reachable functionality that lets users create or edit Field Name values.

Exploitation context

A public Exploit-DB reference exists, but the provided sources do not show CISA KEV listing or confirmed active exploitation. Treat exploitability as publicly documented, not proven in the wild.

Researcher notes

The record is sparse: no CVSS, CWE, CPE, patch, or vendor advisory is included in the bundle. Analysis should remain bounded to Invision Community 4.5.4 and the Field Name XSS claim.

Mitigation direction

  • Inventory Invision Community deployments and identify any 4.5.4 instances.
  • Check official Invision guidance for fixed versions or supported workarounds.
  • Restrict access to Field Name editing while exposure is assessed.
  • Review existing Field Name values for suspicious script-like content.
  • Prioritize session-cookie protections such as HttpOnly and SameSite where applicable.

Validation and detection

  • Confirm whether Invision Community 4.5.4 is present in production or staging.
  • Identify roles that can create or modify Field Name values.
  • Inspect stored Field Name content without rendering it in a browser session.
  • Review web logs for unusual field-management activity around affected systems.
  • Verify remediation against vendor guidance once a fixed version is identified.
Prepared
Confidence
medium
Sources
3

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-29477 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
3Timeline events
1ADP providers
2Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

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.