LiveActive security incident?Get immediate response
CVE Record

CVE-2020-36826: AwesomestCode LiveBot parseMessage.js parseSend cross site scripting

A vulnerability was found in AwesomestCode LiveBot. It has been classified as problematic. Affected is the function parseSend of the file js/parseMessage.js. The manipulation leads to cross site scripting. It is possible to launch the attack remotely. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. Upgrading to version 0.1 is able to address this issue. The name of the patch is 57505527f838d1e46e8f93d567ba552a30185bfa. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-257784.

MediumCVSS 4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-36826 is a cross-site scripting issue in AwesomestCode LiveBot. A logged-in remote user may be able to manipulate message handling so script content runs in another user’s browser. Sources name release 0.1 and commit 57505527 as the fix.

Executive priority

Treat this as a moderate priority where LiveBot is internet-facing or used by many internal users. The issue is not shown as actively exploited, but browser script execution can affect trust in the application and user workflows.

Technical view

The flaw is CWE-79 in the parseSend function in js/parseMessage.js. VulDB rates it CVSS 2.0 score 4.0, with network access, low complexity, and authentication required. Reported impact is partial integrity compromise, with no confidentiality or availability impact in the supplied CVSS vector.

Likely exposure

Exposure is limited to organizations running AwesomestCode LiveBot before the 0.1 release or without commit 57505527f838d1e46e8f93d567ba552a30185bfa. Exact affected versions are not available because the product uses rolling releases.

Exploitation context

The sources say remote exploitation is possible and authenticated access is required. The CVE is not listed as KEV in the bundle, and no cited source here confirms active exploitation in the wild.

Researcher notes

Evidence is limited: no granular affected version range or CPE is provided. The key anchors are VulDB VDB-257784, the CVE record, the GitHub patch commit, and release 0.1. Avoid assuming stored versus reflected XSS without reviewing the patch.

Mitigation direction

  • Upgrade LiveBot to release 0.1 or later.
  • Confirm commit 57505527f838d1e46e8f93d567ba552a30185bfa is present.
  • If upgrade status is unclear, check vendor repository guidance.
  • Restrict LiveBot access to trusted users until updated.

Validation and detection

  • Inventory any deployed AwesomestCode LiveBot instances.
  • Verify running code includes the named patch commit.
  • Confirm deployed build matches release tag 0.1 or later.
  • Review authenticated message-rendering paths for unsafe script execution.
  • Check logs for unusual authenticated message activity.
Prepared
Confidence
medium
Sources
6

Public sources used

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-79: 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-36826 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
Medium
CVSS
4 (2.0)
Known Exploited
No
Published

Vector: AV:N/AC:L/Au:S/C:N/I:P/A:N

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
5Source 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
4CVSS 2.0MediumAV:N/AC:L/Au:S/C:N/I:P/A:N82.9Primary CVE score

Vulnerability scoring details

Base CVSS 2.0 score

4Medium
CVSS 2.0 vector shape for CVE-2020-36826Access VectorAccess ComplexityAuthenticationConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: AV:N/AC:L/Au:S/C:N/I:P/A:N

Access Vector
NetworkAdjacentLocal
Access Complexity
LowMediumHigh
Authentication
NoneSingleMultiple
Confidentiality Impact
CompletePartialNone
Integrity Impact
CompletePartialNone
Availability Impact
CompletePartialNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AwesomestCodeLiveBotn/aListed
Weakness

CWE details

CWE-79

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