Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-54713 low CVSS 3.7

Vulnerability in cakephp/queue (CVE-2026-54713)

Summary

Vulnerability in cakephp/queue (CVE-2026-54713). Risk of unauthorized operations or information disclosure. Exploitable via shouldBeUnique. Mitigation: upgrade to 2.3.1 or later.

Original description

The description as published by the source.

Impact

For jobs with shouldBeUnique = true the queue plugin will generate a 'unique identifier' based on the job class, method and parameters. If user data is supplied, a malicious user could create collisions, resulting in legitimate jobs being dropped.

Patches

Upgrade to 2.3.1

Workarounds

You can disable shouldBeUnique and handle idempotency in application code.

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-54713 has been found in cakephp/queue.
Attackers can target a specific entry point like shouldBeUnique over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/10.
What to do: upgrade cakephp/queue to 2.3.1 or later.
If unsure, ask your IT team or search "cakephp/queue CVE-2026-54713" on the vendor's site.

CVE-2026-54713 (cakephp/queue) — CWE-1023 / CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: shouldBeUnique
Patched: 2.3.1 — apply immediately
Workaround: You can disable shouldBeUnique and handle idempotency in application code.
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-1023) exists in cakephp/queue. Attackers reach the vulnerable code path via shouldBeUnique without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of cakephp/queue. Attack surface: shouldBeUnique.

🔥 Severity

Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.3.1.

🛡️ Workaround

Workaround: You can disable shouldBeUnique and handle idempotency in application code.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'cakephp/queue' . 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

  1. 1
    Identify exposure identify 
    grep -r 'cakephp/queue' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で cakephp/queue を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    You can disable `shouldBeUnique` and handle idempotency in application code.

    パッチが適用されるまでの応急処置として、You can disable shouldBeUnique and handle idempotency in application code. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade cakephp/queue to 2.3.1

    ステージング環境で 2.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

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

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

Affected packages

composer cakephp/queue
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.3.1"}]}]
Packagist cakephp/queue
[{"type":"ECOSYSTEM","events":[{"introduced":"0.1.10"},{"fixed":"2.3.1"}]}]

References

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