Categories
CVE-2026-53592 medium CVSS 4.6

Vulnerability in Laravel (CVE-2026-53592)

Summary

Vulnerability in Laravel (CVE-2026-53592). Risk of unauthorized operations or information disclosure. Exploitable via getQueryParam.

Original description

The description as published by the source.

FreeScout is a free help desk and shared inbox built with PHP's Laravel framework. A Prototype Pollution condition in the getQueryParam function /public/js/main.js and was addressed in version 1.8.139 by blocking URL query keys matching the pattern __proto__. However, this mitigation is incomplete: it only filters top-level __proto__ keys and fails to sanitize nested forms such as b[__proto__][polluted]=PWNED. As a result, an attacker-controlled URL query string can still write into Object.prototype on any page that loads main.js. Version 1.8.223 contains a updated fix.

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-2026-53592 has been found in Laravel.
Attackers can target a specific entry point like getQueryParam over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Laravel CVE-2026-53592" on the vendor's site.

CVE-2026-53592 (Laravel) — CWE-1321 / CVSS v3 4.6
Attack vector: remote (network-reachable)
Attack surface: getQueryParam / __proto__ / Object.prototype / main.js
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.

❓ What is the problem

A vulnerability (CWE-1321) exists in Laravel. Attackers reach the vulnerable code path via getQueryParam.

📍 Affected scope

Check the vendor advisory for the affected versions of Laravel. Attack surface: getQueryParam / __proto__ / Object.prototype / main.js.

🔥 Severity

Severity: Medium (CVSS 4.6/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Laravel を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details