CVE-2026-1251: CWE-639 Authorization Bypass Through User-Controlled Key in psmplugins SupportCandy – Helpdesk & Customer Support Ticket System
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 Analysis
Technical Summary
The SupportCandy – Helpdesk & Customer Support Ticket System plugin for WordPress suffers from an authorization bypass vulnerability classified as CWE-639: Authorization Bypass Through User-Controlled Key. This vulnerability exists in all versions up to and including 3.4.4 within the 'add_reply' function. The root cause is the lack of proper validation on the 'description_attachments' parameter, which accepts user-supplied attachment IDs. Authenticated users with subscriber-level privileges or higher can exploit this flaw to specify arbitrary attachment IDs belonging to other users. By doing so, they can re-associate these attachments to their own support tickets, effectively stealing access to files uploaded by others and simultaneously removing the original owners' access. The vulnerability is an Insecure Direct Object Reference (IDOR) that compromises confidentiality and integrity of user data. The CVSS v3.1 base score is 5.4 (medium severity), reflecting network attack vector, low attack complexity, privileges required, no user interaction, and partial impact on confidentiality and integrity. No known public exploits have been reported yet. The vulnerability affects a widely used WordPress plugin designed for customer support ticket management, which is often deployed in organizations relying on WordPress for their helpdesk solutions. The lack of patch links suggests that a fix may not yet be available, emphasizing the need for immediate mitigation steps.
Potential Impact
This vulnerability allows attackers with minimal privileges (subscriber-level) to access and steal sensitive file attachments uploaded by other users, violating confidentiality. By re-associating attachments to their own tickets, attackers can also disrupt the integrity of ticket data and deny access to legitimate users, potentially causing operational disruptions. Organizations relying on SupportCandy for customer support risk exposure of confidential customer information, intellectual property, or personally identifiable information (PII) contained in attachments. This can lead to data breaches, regulatory non-compliance, reputational damage, and loss of customer trust. Since the attack requires authentication but no user interaction, insider threats or compromised accounts can easily exploit this flaw. The vulnerability does not affect availability directly but can indirectly impact service quality and user confidence in the helpdesk system.
Mitigation Recommendations
Organizations should immediately audit their SupportCandy plugin versions and upgrade to a patched release once available. Until a patch is released, implement strict access controls and monitoring on the WordPress environment, especially limiting subscriber-level user capabilities where possible. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious requests manipulating the 'description_attachments' parameter. Conduct regular reviews of file attachment permissions and ticket associations to detect unauthorized changes. Consider disabling file attachment features temporarily if feasible. Additionally, enforce strong authentication mechanisms and monitor user activity logs for anomalous behavior indicative of exploitation attempts. Engage with the plugin vendor or community to obtain timely security updates and share threat intelligence. Finally, educate users about the risks of account compromise and enforce least privilege principles.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, France, Netherlands, India, Brazil, Japan
CVE-2026-1251: CWE-639 Authorization Bypass Through User-Controlled Key in psmplugins 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
Technical Analysis
The SupportCandy – Helpdesk & Customer Support Ticket System plugin for WordPress suffers from an authorization bypass vulnerability classified as CWE-639: Authorization Bypass Through User-Controlled Key. This vulnerability exists in all versions up to and including 3.4.4 within the 'add_reply' function. The root cause is the lack of proper validation on the 'description_attachments' parameter, which accepts user-supplied attachment IDs. Authenticated users with subscriber-level privileges or higher can exploit this flaw to specify arbitrary attachment IDs belonging to other users. By doing so, they can re-associate these attachments to their own support tickets, effectively stealing access to files uploaded by others and simultaneously removing the original owners' access. The vulnerability is an Insecure Direct Object Reference (IDOR) that compromises confidentiality and integrity of user data. The CVSS v3.1 base score is 5.4 (medium severity), reflecting network attack vector, low attack complexity, privileges required, no user interaction, and partial impact on confidentiality and integrity. No known public exploits have been reported yet. The vulnerability affects a widely used WordPress plugin designed for customer support ticket management, which is often deployed in organizations relying on WordPress for their helpdesk solutions. The lack of patch links suggests that a fix may not yet be available, emphasizing the need for immediate mitigation steps.
Potential Impact
This vulnerability allows attackers with minimal privileges (subscriber-level) to access and steal sensitive file attachments uploaded by other users, violating confidentiality. By re-associating attachments to their own tickets, attackers can also disrupt the integrity of ticket data and deny access to legitimate users, potentially causing operational disruptions. Organizations relying on SupportCandy for customer support risk exposure of confidential customer information, intellectual property, or personally identifiable information (PII) contained in attachments. This can lead to data breaches, regulatory non-compliance, reputational damage, and loss of customer trust. Since the attack requires authentication but no user interaction, insider threats or compromised accounts can easily exploit this flaw. The vulnerability does not affect availability directly but can indirectly impact service quality and user confidence in the helpdesk system.
Mitigation Recommendations
Organizations should immediately audit their SupportCandy plugin versions and upgrade to a patched release once available. Until a patch is released, implement strict access controls and monitoring on the WordPress environment, especially limiting subscriber-level user capabilities where possible. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious requests manipulating the 'description_attachments' parameter. Conduct regular reviews of file attachment permissions and ticket associations to detect unauthorized changes. Consider disabling file attachment features temporarily if feasible. Additionally, enforce strong authentication mechanisms and monitor user activity logs for anomalous behavior indicative of exploitation attempts. Engage with the plugin vendor or community to obtain timely security updates and share threat intelligence. Finally, educate users about the risks of account compromise and enforce least privilege principles.
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: 2/26/2026, 7:00:47 PM
Last updated: 3/17/2026, 8:45:46 AM
Views: 120
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.