Vulnerability in laravel/framework (CVE-2026-102279)
Summary
Vulnerability in laravel/framework (CVE-2026-102279). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 13.30.0 or later.
Original description
The description as published by the source.
Impact
When APP_DEBUG=true, attacker-controlled input is passed to a Tippy.js tooltip configured with allowHTML: true, enabling DOM-based XSS during mouse hover.
Patches
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-2026-102279 has been found in laravel/framework.
Risk of unauthorized operations or information disclosure. CVSS score: 3.1/10.
What to do: upgrade laravel/framework to 13.30.0 or later.
If unsure, ask your IT team or search "laravel/framework CVE-2026-102279" on the vendor's site.
CVE-2026-102279 (laravel/framework) — CWE-80 / CVSS v3 3.1
Attack vector: remote (network-reachable) / unauthenticated
Patched: 13.30.0 — 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.
A vulnerability (CWE-80) exists in laravel/framework.
Check the vendor advisory for the affected versions of laravel/framework.
Severity: Low (CVSS 3.1/10). Risk of unauthorized operations or information disclosure.
Update to 13.30.0.
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 'laravel/framework' . 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 'laravel/framework' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
laravel/frameworkを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade laravel/framework to 13.30.0ステージング環境で 13.30.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com