LiveActive security incident?Get immediate response
CVE Record

CVE-2015-10089: flame.js cross site scripting

A vulnerability classified as problematic has been found in flame.js. This affects an unknown part. The manipulation leads to cross site scripting. It is possible to initiate the attack remotely. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The patch is named e6c49b5f6179e31a534b7c3264e1d36aa99728ac. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-222291.

MediumCVSS 4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2015-10089 is a cross-site scripting issue in flame.js. A logged-in remote attacker could influence page content so users' browsers run unintended script. Published impact is integrity-only, with no confidentiality or availability impact claimed in the source bundle.

Executive priority

Handle during normal vulnerability remediation, with higher priority for externally reachable authenticated applications using flame.js. The business risk is browser-side content manipulation, not server takeover, based on available evidence.

Technical view

The issue is classified as CWE-79 XSS in flame.js. CVSS v2 is 4.0: network-accessible, low complexity, authentication required, partial integrity impact, no confidentiality or availability impact. A fixing commit is identified, but affected and unaffected versions are unavailable because the project does not use versioning.

Likely exposure

Exposure is likely limited to applications that include flame.js, especially unpatched copies or forks. Version-based detection is unreliable because the product does not use versioning, so teams must identify usage and compare source state against the named patch commit.

Exploitation context

The source bundle says the attack can be initiated remotely and requires authentication. It does not identify public exploitation, weaponized details, or inclusion in CISA KEV. Treat active exploitation as unconfirmed.

Researcher notes

Evidence is thin: the affected component is unknown and releases are not versioned. The most reliable anchors are the VulDB entry, GitHub PR 209, and the named patch commit. No source in the bundle supports active exploitation.

Mitigation direction

  • Apply or backport commit e6c49b5f6179e31a534b7c3264e1d36aa99728ac.
  • Inventory applications and repositories for bundled flame.js copies.
  • Compare local flame.js code against the patched upstream commit.
  • Check upstream project guidance before assuming version-based remediation.
  • Prioritize regression testing around rendering of user-controlled content.

Validation and detection

  • Confirm whether any application ships flame.js client-side code.
  • Verify the patch commit is present in deployed source bundles.
  • Review GitHub pull request 209 for remediation context.
  • Run non-destructive XSS regression tests around affected rendering paths.
  • Document findings where version evidence is unavailable.
Prepared
Confidence
medium
Sources
6

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-2015-10089 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-2015-10089Access 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
n/aflame.jsn/aListed
Weakness

CWE details

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.