Cross-Site Scripting (XSS) in Laravel (CVE-2026-71233)
Summary
Cross-site scripting in Laravel (CVE-2026-71233). Confidential information can be exposed externally. Exploitable via PUT /api/v1/invoices/{id}.
Original description
The description as published by the source.
InvoiceNinja v5-stable renders an invoice or quote's "terms" field in the client portal using Laravel Blade's raw output directive {!! $entity->terms !!} (resources/views/portal/ninja2020/invoices/includes/terms.blade.php) with no HTML sanitization. StoreInvoiceRequest.php only strips newlines from the field and does not purify HTML. An authenticated user with invoice creation access can set the terms field via the REST API (PUT /api/v1/invoices/{id}) to an HTML/JavaScript payload that executes in the client's browser when they view the invoice, enabling session cookie theft and client account takeover. This is a distinct code path from the previously published invoice line-item description field XSS (GHSA-98wm-cxpw-847p / CVE-2026-33628).
Source: GitHub Security Advisories (Global) 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-71233 has been found in Laravel.
Attackers can target a specific entry point like PUT /api/v1/invoices/{id} over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Laravel CVE-2026-71233" on the vendor's site.
CVE-2026-71233 (Laravel) — CWE-79 / CVSS v3 8.7
Attack vector: remote (network-reachable)
Attack surface: PUT /api/v1/invoices/{id}
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. Attackers reach the vulnerable code path via PUT /api/v1/invoices/{id}.
Check the vendor advisory for the affected versions of Laravel. Attack surface: PUT /api/v1/invoices/{id}.
Severity: High (CVSS 8.7/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual PUT /api/v1/invoices/{id} requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Laravel を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'PUT /api/v1/invoices/{id}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PUT /api/v1/invoices/{id}への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against PUT /api/v1/invoices/{id} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web nvd.nist.gov
- web github.com
- web github.com