LiveActive security incident?Get immediate response
CVE Record

CVE-2014-125078: yanheven console horizon.instances.js cross site scripting

A vulnerability was found in yanheven console and classified as problematic. Affected by this issue is some unknown functionality of the file horizon/static/horizon/js/horizon.instances.js. The manipulation leads to cross site scripting. The attack may be launched remotely. The patch is identified as 32a7b713468161282f2ea01d5e2faff980d924cd. It is recommended to apply a patch to fix this issue. VDB-218354 is the identifier assigned to this vulnerability.

MediumCVSS 4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2014-125078 is a cross-site scripting issue in yanheven console. A remote authenticated user could manipulate behavior in horizon.instances.js and affect page integrity. The public record names a patch commit, but does not provide affected version ranges or detailed exploit conditions.

Executive priority

Treat this as a moderate-priority web application fix. It is not listed as actively exploited in the provided sources, but XSS in an administrative console can create business risk where many users or broad privileges exist.

Technical view

The issue is classified as CWE-79 XSS in horizon/static/horizon/js/horizon.instances.js. CVSS v2 is 4.0 with network access, low complexity, authentication required, no confidentiality impact, partial integrity impact, and no availability impact. Patch commit 32a7b713468161282f2ea01d5e2faff980d924cd is cited.

Likely exposure

Exposure appears limited to deployments of yanheven console, especially where authenticated users can access the affected console UI. The source bundle does not identify vulnerable versions, CPEs, or whether downstream forks are affected.

Exploitation context

The sources say the attack may be launched remotely and CVSS indicates authentication is required. There is no KEV listing and no cited source in the bundle supports active exploitation. Public evidence is incomplete on exploit maturity.

Researcher notes

Key gaps are affected versions, exact vulnerable input path, and exploit maturity. Validate against the patch diff and deployed artifact lineage. Avoid assuming OpenStack Horizon exposure unless yanheven console or a derived codebase is confirmed.

Mitigation direction

  • Check whether yanheven console is deployed or embedded in internal platforms.
  • Apply the cited patch commit or vendor-provided fixed release.
  • Restrict console access to trusted authenticated users only.
  • Review local forks for changes around horizon.instances.js.
  • Monitor vendor or project guidance for affected version clarification.

Validation and detection

  • Inventory yanheven console deployments and any forks using horizon.instances.js.
  • Verify the patched commit is present in deployed source or build artifacts.
  • Run authorized XSS regression tests against the affected UI behavior.
  • Confirm console routes require authentication and least-privilege access.
  • Review recent console activity for suspicious authenticated user actions.
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.

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-2014-125078 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
4Source 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-2014-125078Access 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
yanhevenconsolen/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.