LiveActive security incident?Get immediate response
CVE Record

CVE-2020-35305: Cross site scripting (XSS) in gollum 5.0 to 5.1.2 via the filename parameter to the 'New Page' dialog.

Cross site scripting (XSS) in gollum 5.0 to 5.1.2 via the filename parameter to the 'New Page' dialog.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-35305 is a reported cross-site scripting issue in Gollum versions 5.0 through 5.1.2. The issue involves the filename parameter in the New Page dialog. If exploitable in a deployed wiki, it could let attacker-controlled script run in another user’s browser. The provided sources do not include CVSS, confirmed exploitation, or a named fixed version.

Executive priority

Prioritize discovery first. This is a web-facing XSS class issue, but the bundle lacks severity scoring, exploitation evidence, and patch detail. If affected Gollum is internet-accessible or writable by untrusted users, handle as a near-term remediation item.

Technical view

The CVE describes XSS in Gollum 5.0 to 5.1.2 through handling of the filename parameter in the New Page dialog. The source bundle does not provide CWE, CVSS metrics, exploit prerequisites, authentication requirements, or patch details. Treat exposure as version- and feature-dependent until validated against deployed Gollum instances and vendor release guidance.

Likely exposure

Exposure is most likely where Gollum 5.0 through 5.1.2 is deployed and users can access the New Page dialog. Risk rises if untrusted or lower-privileged users can create pages or influence page filenames.

Exploitation context

The provided CVE data does not show CISA KEV listing or other evidence of active exploitation. It also does not include exploit details. Assessment should focus on whether affected Gollum versions are present and whether page creation is available to untrusted users.

Researcher notes

Evidence is sparse. The CVE identifies product family, affected versions, and input location, but omits CVSS, CWE, patch commit, authentication context, and exploit maturity. Avoid assuming a fixed version from the v5.1.2 reference because the description states 5.0 to 5.1.2 are affected.

Mitigation direction

  • Inventory Gollum deployments and confirm whether versions 5.0 through 5.1.2 are present.
  • Check official Gollum release guidance for the fixed or recommended version.
  • Upgrade or replace affected deployments when vendor guidance identifies a safe version.
  • Restrict wiki page creation to trusted users until remediation is confirmed.
  • Review browser security controls such as CSP as defense in depth.

Validation and detection

  • Confirm deployed Gollum versions from package metadata or application release information.
  • Verify whether the New Page dialog is reachable by untrusted users.
  • Review access controls for page creation and filename submission workflows.
  • Check application logs for unusual page creation or filename activity.
  • After remediation, confirm the deployed version matches vendor guidance.
Prepared
Confidence
medium
Sources
5

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-35305 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
4Source 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.