Skip to main content

Faveo Helpdesk CVE-2026-111676

| EUVDEUVD-2026-102967 MEDIUM
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-10-16 VulnCheck GHSA-8f6x-fr2m-f6wc
5.3
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privilege agent
  2. Exploit
    Enumerate sequential ticketid values
  3. Execution
    Call GET /ticket/tooltip per id
  4. Impact
    Read cross-department tickets and PII

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
Exploitation Conditions

Requires a valid authenticated Faveo Helpdesk agent account (PR:L); exploitation targets the getTooltip handler reached via GET /ticket/tooltip with an attacker-controlled sequential ticketid parameter. The endpoint is a standard application route, so exploitation works against default configurations with no special feature toggle needed. Limiting factors: the attacker must first possess or obtain agent-level credentials, the flaw is read-only (confidentiality disclosure of ticket conversations, customer PII, and internal notes - no modification or denial of service), and impact scales only with the number of enumerable ticket IDs.

Impact

This is a moderate, confidentiality-only broken access control (IDOR) issue, not a top-tier priority. The input CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) and the 5.3 base score are internally consistent with the description: network-reachable, low complexity, but requiring an authenticated agent account (PR:L), with only low confidentiality impact (VC:L) and no integrity or availability impact. No EPSS score, no CISA KEV listing, and no explicit POC/exploit-code flag were provided in the input, so there is no signal of active or widespread exploitation - SSVC-style, this reads as 'exploitation: none proven' with technical impact 'partial' and low automatability beyond trivial ID enumeration. The one aggravating factor is that a detailed public technical write-up (hackmd) and a VulnCheck advisory describe the exact vulnerable endpoint and the sequential-ID enumeration method, which materially lowers the barrier to building an exploit even though no packaged exploit is listed. Net: a real but limited insider/low-privilege data-exposure risk, appropriate for routine patching rather than emergency response. Note one labeling conflict: the input Tag 'Authentication Bypass' contradicts the description and CWE-639 (authorization bypass) - this is an authenticated authorization flaw, not an authentication bypass.

Exploit ScenarioDerived

An attacker who already holds a low-privileged Faveo agent account (or a compromised agent login) issues repeated GET /ticket/tooltip requests while incrementing the ticketid parameter, harvesting ticket conversations from departments they are not authorized to view. Because the getTooltip handler omits a department authorization check, the agent can systematically scrape customer PII and internal agent notes. No packaged exploit is listed, but a public technical write-up documents the exact endpoint and enumeration technique.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 16, 2026

Broken access control in Faveo Helpdesk through 2.0.3 lets any authenticated agent read ticket conversations, customer personally identifiable information, and internal agent notes belonging to other departments by enumerating sequential ticketid values against the GET /ticket/tooltip endpoint (CWE-639, IDOR). The flaw is read-only, requires a low-privileged authenticated agent account (PR:L in the published CVSS vector), and works against default configurations because no special feature toggle or non-default setting is needed; impact scales with how many ticket IDs the attacker can walk. No CISA KEV entry exists for this CVE and there is no confirmed active exploitation, though a public technical writeup documents the attack path; the assigned CVSS score is 5.3.

RemediationAI

No vendor-released patch was identified at time of analysis; the GitHub references in the advisory point to the vulnerable v2.0.3 source rather than a fix commit or tagged release, so no exact fix version can be cited. Until an upstream fix is published, the most direct mitigation is to add object-level authorization to the getTooltip path so the returned ticket is filtered by the requesting agent's department/team (or to remove/disable the GET /ticket/tooltip route entirely) - the trade-off is loss of the agent hover-preview feature until the route is restored. As a compensating network control, block or restrict /ticket/tooltip at the reverse proxy or WAF for all but trusted agent subnets; this breaks the tooltip UI for legitimate remote agents. Because IDs are sequential, enforce per-agent rate limiting and alerting on GET /ticket/tooltip enumeration patterns, and audit agent accounts for unnecessary department membership; rate limiting only slows a patient attacker rather than stopping the disclosure, and does not address the missing authorization check. Review ticket tooltip logs and access records for evidence of cross-department ticketid enumeration, and treat any exposed customer PII or internal notes as a data-breach candidate requiring notification review. Monitor https://github.com/faveosuite/faveo-helpdesk and https://www.vulncheck.com/advisories/faveo-helpdesk-through-2.0.3-broken-access-control-via-ticket-tooltip-endpoint for a patched release, and apply it as soon as a fixed version is published.

Affected VersionsENISA

faveo-helpdesk 0 ≤2.0.3

Affected Packages

euvd faveo_helpdesk no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Faveo Helpdesk is a PHP/Laravel-based open-source support ticketing system, evidenced by the referenced controller path app/Http/Controllers/Agent/helpdesk/TicketController.php and the route definition in routes/web.php (line 350), which wires GET /ticket/tooltip to the getTooltip handler (lines 2356-2374 of the v2.0.3 controller). The root cause class is CWE-639, Authorization Bypass Through User-Controlled Key: the handler accepts an attacker-supplied ticketid parameter and returns ticket tooltip content without verifying that the requesting agent's department or team is authorized for that record. Because ticket identifiers are sequential and the route performs no object-level authorization check, an agent scoped to one department can retrieve records belonging to another. The supplied CPE, cpe:2.3:a:faveosuite:faveo-helpdesk:*:*:*:*:*:*:*:*, is a wildcard entry, and the VulnCheck advisory scopes the issue to versions through 2.0.3, so any deployment at or below that release and exposing the agent tooltip route should be treated as affected. The technique is a classic horizontal privilege escalation on a read path: disclosure only (VC:L, VI:N, VA:N in the assessed 3.1 vector), with no code execution, write, or denial-of-service primitive demonstrated.

Know when Faveo Helpdesk gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 5.3 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 4.3 MEDIUM

Network-reachable endpoint with low complexity, but requires an authenticated agent account (PR:L); impact is read-only cross-department data disclosure, so C:L and I/A:N.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

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.

Threat Intelligence Overview

EPSS Score
0.3%
Top 85% exploitable
Prevalence
Low
niche open-source/commercial helpdesk, limited enterprise deployment footprint
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy