Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-1251: CWE-639 Authorization Bypass Through User-Controlled Key in psmplugins SupportCandy – Helpdesk & Customer Support Ticket System

0
Medium
VulnerabilityCVE-2026-1251cvecve-2026-1251cwe-639
Published: Sat Jan 31 2026 (01/31/2026, 06:39:23 UTC)
Source: CVE Database V5
Vendor/Project: psmplugins
Product: SupportCandy – Helpdesk & Customer Support Ticket System

Description

The SupportCandy – Helpdesk & Customer Support Ticket System plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.4.4 via the 'add_reply' function due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with subscriber-level access and above, to steal file attachments uploaded by other users by specifying arbitrary attachment IDs in the 'description_attachments' parameter, re-associating those files to their own tickets and removing access from the original owners.

AI-Powered Analysis

AILast updated: 01/31/2026, 07:12:06 UTC

Technical Analysis

CVE-2026-1251 is an authorization bypass vulnerability classified under CWE-639 (Authorization Bypass Through User-Controlled Key) affecting the SupportCandy Helpdesk & Customer Support Ticket System plugin for WordPress, versions up to and including 3.4.4. The vulnerability arises from insufficient validation of user-controlled input in the 'add_reply' function, specifically the 'description_attachments' parameter. Authenticated users with subscriber-level privileges or higher can exploit this flaw by specifying arbitrary attachment IDs, which allows them to re-associate file attachments originally uploaded by other users to their own support tickets. This effectively steals access to those files and removes the original owners' access rights. The attack vector is remote network-based (AV:N), requires low attack complexity (AC:L), and only requires privileges equivalent to subscriber level (PR:L), with no user interaction (UI:N). The vulnerability impacts confidentiality and integrity by enabling unauthorized access and modification of file associations but does not affect availability. No patches were linked at the time of publication, and no active exploits have been reported. The vulnerability is significant in environments where sensitive or confidential attachments are handled through the SupportCandy plugin, potentially exposing private customer data or internal documents.

Potential Impact

For European organizations, this vulnerability poses a risk of unauthorized disclosure and modification of sensitive attachments managed within the SupportCandy plugin on WordPress sites. Organizations relying on this plugin for customer support and ticket management may face data confidentiality breaches, potentially violating GDPR requirements concerning personal data protection. The ability for low-privilege users to access and reassign files could lead to insider threats or exploitation by compromised accounts. This could damage organizational reputation, lead to regulatory fines, and disrupt customer trust. Since the vulnerability does not affect availability, service disruption is less likely, but the integrity and confidentiality impacts are significant, especially for sectors handling sensitive customer information such as finance, healthcare, and public services. The lack of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits over time.

Mitigation Recommendations

European organizations should implement the following specific mitigations: 1) Immediately audit user roles and restrict subscriber-level permissions to the minimum necessary, limiting access to the SupportCandy plugin features. 2) Monitor and log attachment access and modifications within the plugin to detect suspicious re-association activities. 3) Apply vendor patches or updates as soon as they become available; if no patch exists, consider temporarily disabling the plugin or restricting its use to trusted users only. 4) Employ Web Application Firewalls (WAFs) with custom rules to detect and block anomalous requests targeting the 'description_attachments' parameter. 5) Conduct regular security assessments of WordPress plugins, focusing on access control and input validation. 6) Educate support staff and users about the risks of unauthorized access and encourage strong authentication practices to reduce account compromise likelihood.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2026-01-20T19:04:14.485Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 697da7ecac06320222134c3b

Added to database: 1/31/2026, 6:57:48 AM

Last enriched: 1/31/2026, 7:12:06 AM

Last updated: 1/31/2026, 9:04:29 AM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats