Cross-Site Scripting (XSS) in Laravel Sharp (CVE-2025-62798)
Summary
Cross-site scripting in Laravel Sharp (CVE-2025-62798). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 9.11.1 or later.
Original description
The description as published by the source.
Sharp is a content management framework built for Laravel as a package. Prior to 9.11.1, 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. The issue has been fixed in v9.11.1 .
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-62798 has been found in Laravel Sharp.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade Laravel Sharp to 9.11.1 or later.
If unsure, ask your IT team or search "Laravel Sharp CVE-2025-62798" on the vendor's site.
CVE-2025-62798 (Laravel Sharp) — CWE-79 / CVSS v3 5.4
Attack vector: remote (network-reachable)
Patched: 9.11.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in Laravel Sharp.
Check the vendor advisory for the affected versions of Laravel Sharp.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 9.11.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Sharp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Sharp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Sharpを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Laravel Sharp to 9.11.1ステージング環境で 9.11.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。