How severe is GHSA-5m5x-9j46-h678?

No CVSS score has been assigned to GHSA-5m5x-9j46-h678 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5m5x-9j46-h678?

GHSA-5m5x-9j46-h678 affects the following packages: element-plus (npm). Ecosystems affected: npm.

How do I fix GHSA-5m5x-9j46-h678?

The records we use list no patched version of element-plus for GHSA-5m5x-9j46-h678. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-5m5x-9j46-h678 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for element-plus, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-5m5x-9j46-h678 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-5m5x-9j46-h678 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5m5x-9j46-h678 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-5m5x-9j46-h678?

GHSA-5m5x-9j46-h678 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 15th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-5m5x-9j46-h678?

GHSA-5m5x-9j46-h678 is classified as Cross-site Scripting (XSS) (CWE-79), Open Redirect (CWE-601). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-5m5x-9j46-h678 published, and has it been updated?

GHSA-5m5x-9j46-h678 was published on September 9, 2025 and was last updated on September 12, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Element Plus Link component (el-link) implements insufficient input validation for the href attributeGHSA-5m5x-9j46-h678

Fix: element-plus/element-plus#21711

GHSA-5m5x-9j46-h678 is a Cross-site Scripting (XSS) vulnerability in element-plus. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asCVE-2025-57665

Published

Sep 9, 2025

Updated

Sep 12, 2025

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for GHSA-5m5x-9j46-h678.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs15th percentile — riskier than 15% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

5Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

element-plusnpm

796Kdownloads / week

Description

Element Plus Link component (el-link) prior to 2.11.0 implements insufficient input validation for the href attribute, creating a security abstraction gap that obscures URL-based attack vectors. The component passes user-controlled href values directly to underlying anchor elements without protocol validation, URL sanitization, or security headers. This allows attackers to inject malicious URLs using dangerous protocols (javascript:, data:, file:) or redirect users to external malicious sites. While native HTML anchor elements present similar risks, UI component libraries bear additional responsibility for implementing security safeguards and providing clear risk documentation. The vulnerability enables XSS attacks, phishing campaigns, and open redirect exploits affecting applications that use Element Plus Link components with user-controlled or untrusted URL inputs. As of version 2.11.0, Element Plus have clearly documented the risks inherent with the component.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`element-plus`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

element-pluselement-plus

≤ 2.10.6

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for element-plus, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of element-plus for GHSA-5m5x-9j46-h678. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.