Skip to main content

UVdesk Support Center CVE-2026-105029

| EUVDEUVD-2026-91856 MEDIUM
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-10-03 disclosure@vulncheck.com GHSA-vqxj-p9x3-9jmp
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 any customer
  2. Exploit
    Supply arbitrary ticket ID to rateTicket endpoint
  3. Execution
    Bypass missing ownership check
  4. Impact
    Submit or overwrite satisfaction ratings on others' tickets

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 customer account on the UVdesk support-center portal (PR:L). The attacker must supply or enumerate ticket IDs owned by other customers; because the vulnerable rateTicket action called find($id) without a customer filter, any supplied ID is loaded without an ownership check. Exploitation is limited to submitting or altering satisfaction ratings - it grants no read access to ticket content and no code execution. Only support-center-bundle versions before 1.1.3.3 are affected; patched builds reject tickets not owned by the requesting customer with an 'Invalid rating' response.

Impact

This is a medium-severity authorization flaw (CWE-639 IDOR), not a critical priority. The provided CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) confirms a network-reachable, low-complexity endpoint but requires an authenticated customer account (PR:L), and the only impact is low integrity (VI:L) - tampering with satisfaction ratings - with no confidentiality (VC:N) or availability (VA:N) impact. No EPSS score, SSVC decision, or KEV status was provided in the input, so there is no signal of widespread or automatable exploitation; KEV is absent, meaning no confirmed active exploitation. A public technical writeup exists (hackmd.io/@leediay/idor-rate-ticket_uvdesk) and the fixing commit is public, so exploitation details are available, but no formal POC=YES flag was supplied. The signals are internally consistent: the flaw is genuine and trivially exploitable by any logged-in customer, but its real-world blast radius is small because it only affects the integrity of ticket satisfaction ratings, not the tickets' content or the system itself. Net: a legitimate low-to-medium data-integrity bug worth patching, not an emergency.

Exploit ScenarioDerived

A registered customer on a UVdesk support portal logs in and sends a rateTicket request supplying a ticket ID belonging to a different customer. Because the endpoint loaded the ticket by ID alone without an ownership check, the attacker's rating is accepted, letting them submit or overwrite satisfaction ratings on tickets they do not own. A public technical writeup detailing this IDOR is available, lowering the skill needed to reproduce it.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 03, 2026

An insecure direct object reference (IDOR) in the UVdesk support-center-bundle before version 1.1.3.3 lets any authenticated customer submit or overwrite the satisfaction rating on tickets owned by other customers by supplying arbitrary ticket IDs to the rateTicket action. The flaw is limited to rating tampering: it grants no read access to other customers' ticket content, no account takeover, and no code execution, which is why it is assessed as medium severity (CVSS 3.1 base 5.3, AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N). Exploitation requires a valid, low-privileged customer account and knowledge or enumeration of target ticket IDs; no public exploit code was identified at time of analysis, and the issue is fixed upstream in 1.1.3.3.

RemediationAI

Upgrade the UVdesk support-center-bundle to 1.1.3.3 or later - the tagged maintenance release referenced by the vendor changelog - or apply the upstream patch commit 3fa884a3adf0f317f354f83a1f9fa531234a551f, which changes the rateTicket lookup from find($id) to findOneBy(['id' => $id, 'customer' => $customer]) and rejects foreign tickets with an 'Invalid rating' response; note that patch status is confirmed at the commit/release level rather than through an independent vendor security bulletin. If upgrading is not immediately possible, compensating controls include temporarily disabling or removing the customer-facing ticket rating route so the rateTicket endpoint is unreachable, which eliminates the attack surface at the cost of losing satisfaction survey data collection, or fronting the helpdesk with a reverse-proxy/WAF rule that restricts POSTs to the rating endpoint to same-session ticket IDs - an effective but brittle filter that can be bypassed if IDs are legitimately shared. Additional context is available in the VulnCheck advisory (https://www.vulncheck.com/advisories/uvdesk-support-center-bundle-before-1.1.3.3-idor-via-rateticket-ticket-rating-endpoint) and the reporter's write-up (https://hackmd.io/@leediay/idor-rate-ticket_uvdesk).

Affected VersionsENISA

community-skeleton 0 <1.1.8
support-center-bundle 0 <1.1.3.3

Affected Packages

euvd community_skeleton fix: 1.1.8
euvd support_center_bundle fix: 1.1.3.3

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in euvd

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

Technical ContextAI · show details

The support-center-bundle is the Symfony/PHP customer-facing helpdesk component of UVdesk, routing ticket creation, replies and satisfaction ratings through Controller/Ticket.php. The vulnerable rateTicket() action resolved the target ticket with Doctrine's $repository->find($id), which loads a Ticket entity by primary key alone and performs no ownership or authorization filtering. Because the object reference (the ticket ID) is attacker-controlled and the loaded entity is trusted implicitly, any authenticated customer could reference another customer's ticket and write a rating to it - the classic CWE-639 Authorization Bypass Through User-Controlled Key pattern. The upstream fix replaces the bare lookup with findOneBy(['id' => $id, 'customer' => $customer]) and returns an 'Invalid rating' JSON error when no ticket matching both the ID and the requesting customer is found, scoping the write to objects the caller actually owns. The same commit also removes broad try/catch blocks around ticket and thread creation and narrows an htmlspecialchars/str_replace sanitization call, none of which change the rating authorization behavior but indicate a broader hardening pass in the 1.1.3.x line.

Know when PHP 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:N/VI:L/VA:N/SC:N/SI:N/SA:N
vuln.today AI 4.3 MEDIUM

Authenticated customer account required (PR:L) over a network-reachable, low-complexity endpoint; impact is limited to tampering with ratings (I:L), with no confidentiality or availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/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
None
Vulnerable system: Integrity
Low
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

1
Patch available
Oct 03, 2026 - 01:01 EUVD

DescriptionCVE.org

UVdesk support-center-bundle before 1.1.3.3 contains an insecure direct object reference vulnerability in the rateTicket action of Controller/Ticket.php that allows authenticated customers to rate other customers' tickets. Attackers can supply arbitrary ticket IDs, which are loaded without an ownership check, to submit or change satisfaction ratings on tickets owned by other customers.

Threat Intelligence Overview

EPSS Score
0.2%
Top 91% exploitable
Prevalence
Low
niche open-source PHP/Symfony helpdesk, limited enterprise footprint
Social Media
1
Sightings
Data Quality
5 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.2%
Patch available Yes
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
Poc
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

More in PHP

View all
CVE-2019-11043 CRITICAL POC
9.8 Oct 28

In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it

CVE-2012-1823 CRITICAL POC
9.8 May 11

sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not

CVE-2016-1555 CRITICAL POC
9.8 Apr 21

(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear

CVE-2018-11138 CRITICAL POC
9.8 May 31

The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by

CVE-2024-11680 CRITICAL POC
9.8 Nov 26

ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C

CVE-2025-49113 CRITICAL POC
9.9 Jun 02

Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au

CVE-2017-9841 CRITICAL POC
9.8 Jun 27

Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c

CVE-2025-0108 HIGH POC
8.8 Feb 12

Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers

CVE-2021-25298 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2021-25296 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2013-4983 CRITICAL POC
10.0 Sep 10

The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

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