LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27701: LiveCodes vulnerable to JavaScript Injection via untrusted PR title in i18n-update-pull workflow

LiveCode is an open-source, client-side code playground. Prior to commit e151c64c2bd80d2d53ac1333f1df9429fe6a1a11, LiveCode's `i18n-update-pull` GitHub Actions workflow is vulnerable to JavaScript injection. The title of the Pull Request associated with the triggering issue comment is interpolated directly into a `actions/github-script` JavaScript block using a GitHub Actions template expression. An attacker who opens a PR with a crafted title can inject arbitrary JavaScript that executes with the privileges of the CI bot token (`CI_APP_ID` / `CI_APP_PRIVATE_KEY`), enabling exfiltration of repository secrets and unauthorized GitHub API operations. Commit e151c64c2bd80d2d53ac1333f1df9429fe6a1a11 fixes the issue.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-27701 affects LiveCodes’ GitHub Actions automation, not the client-side playground runtime directly. A malicious pull request title could be interpreted as JavaScript inside a workflow, allowing actions under the CI bot’s privileges. The main business risk is compromise of repository secrets and unauthorized GitHub operations if the vulnerable workflow is reachable.

Executive priority

Prioritize remediation for any organization maintaining LiveCodes forks or CI workflows with repository secrets. Treat as high urgency for maintainers because compromise could expose secrets or allow unauthorized repository changes. Lower priority if you only use LiveCodes and do not run its GitHub Actions workflows.

Technical view

Before commit e151c64c2bd80d2d53ac1333f1df9429fe6a1a11, LiveCodes’ i18n-update-pull workflow interpolated an untrusted PR title into an actions/github-script JavaScript block. This is CWE-94 code injection. The advisory states arbitrary JavaScript could run with CI bot token credentials, including CI_APP_ID and CI_APP_PRIVATE_KEY.

Likely exposure

Exposure is limited to LiveCodes repositories or derived forks using the vulnerable i18n-update-pull GitHub Actions workflow before the fixing commit. Organizations only consuming hosted LiveCodes should verify relevance, because the described issue is in repository CI automation.

Exploitation context

Sources describe a crafted PR title and a triggering issue comment as prerequisites. The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The impact centers on CI token privileges, repository secrets, and GitHub API actions.

Researcher notes

The provided record assigns CVSS 4.0 score 8.8, vector AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N. Affected version is listed as before commit e151c64c2bd80d2d53ac1333f1df9429fe6a1a11. Evidence is limited to the CVE record, GitHub advisory, and fixing commit.

Mitigation direction

  • Update LiveCodes to commit e151c64c2bd80d2d53ac1333f1df9429fe6a1a11 or later.
  • Review forks for the same vulnerable workflow pattern.
  • Rotate CI_APP_ID, CI_APP_PRIVATE_KEY, and related CI secrets if exposure is suspected.
  • Review GitHub Actions runs and audit logs for unusual bot-token activity.
  • Follow the GitHub advisory for any additional vendor guidance.

Validation and detection

  • Confirm the repository contains commit e151c64c2bd80d2d53ac1333f1df9429fe6a1a11 or equivalent fix.
  • Inspect i18n-update-pull workflow for direct PR title interpolation into github-script.
  • Inventory repositories forked from or based on live-codes/livecodes.
  • Check whether CI_APP_ID and CI_APP_PRIVATE_KEY were available to the workflow.
  • Review recent workflow logs for unexpected repository or GitHub API activity.
Prepared
Confidence
high
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-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-27701 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 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA: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
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 4.0HighCVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.8High
CVSS 4.0 vector shape for CVE-2026-27701Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
live-codeslivecodes< e151c64c2bd80d2d53ac1333f1df9429fe6a1a11Listed
Weakness

CWE details

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

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.