Summary
A Cross-Site Scripting (XSS) vulnerability was discovered in code16/sharp when rendering content using the SharpShowTextField component.
In affected versions, expressions wrapped in {{ & }} were evaluated by Vue. This allowed attackers to inject arbitrary JavaScript or HTML that executes in the browser when the field is displayed.
For example, if a field’s value contains {{ Math.random() }}, it will be executed instead of being displayed as text.
Mitigation / Workarounds
Sanitize or encode any user-provided data that may include ({{ & }}) before displaying it in a SharpShowTextField.
Impact
Attackers who can control content rendered through SharpShowTextField could execute arbitrary JavaScript in the context of an authenticated user’s browser.
This could lead to:
- Theft of user session tokens.
- Unauthorized actions performed on behalf of users.
- Injection of malicious content into the admin panel.
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
CVE-2025-62798 has a CVSS score of 5.4 (Medium). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (9.11.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
The issue has been fixed in v9.11.1 of code16/sharp package.
Frequently Asked Questions
- What is CVE-2025-62798? CVE-2025-62798 is a medium-severity cross-site scripting (XSS) vulnerability in code16/sharp (composer), affecting versions < 9.11.1. It is fixed in 9.11.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- How severe is CVE-2025-62798? CVE-2025-62798 has a CVSS score of 5.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of code16/sharp are affected by CVE-2025-62798? code16/sharp (composer) versions < 9.11.1 is affected.
- Is there a fix for CVE-2025-62798? Yes. CVE-2025-62798 is fixed in 9.11.1. Upgrade to this version or later.
- Is CVE-2025-62798 exploitable, and should I be worried? Whether CVE-2025-62798 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-62798 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-62798? Upgrade
code16/sharpto 9.11.1 or later.