Vulnerability in Faveo Helpdesk (CVE-2026-111676)
Summary
Vulnerability in Faveo Helpdesk (CVE-2026-111676). Risk of unauthorized operations or information disclosure. Exploitable via GET /ticket/tooltip.
Original description
The description as published by the source.
Faveo Helpdesk through 2.0.3 contains a broken access control vulnerability that allows authenticated agents to read tickets in other departments via the getTooltip handler. Attackers can enumerate sequential ticketid values on GET /ticket/tooltip to read ticket conversations, including customer personal data and internal agent notes.
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-111676 has been found in Faveo Helpdesk.
Attackers can target a specific entry point like GET /ticket/tooltip over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Faveo Helpdesk CVE-2026-111676" on the vendor's site.
CVE-2026-111676 (Faveo Helpdesk) — CWE-639 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /ticket/tooltip
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-639) exists in Faveo Helpdesk. Attackers reach the vulnerable code path via GET /ticket/tooltip.
Check the vendor advisory for the affected versions of Faveo Helpdesk. Attack surface: GET /ticket/tooltip.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
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 GET /ticket/tooltip 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・依存マニフェストで Faveo Helpdesk を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'GET /ticket/tooltip' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /ticket/tooltipへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against GET /ticket/tooltip on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。