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-25321: Missing Authorization in PSM Plugins SupportCandy

0
Medium
VulnerabilityCVE-2026-25321cvecve-2026-25321
Published: Thu Feb 19 2026 (02/19/2026, 08:26:55 UTC)
Source: CVE Database V5
Vendor/Project: PSM Plugins
Product: SupportCandy

Description

Missing Authorization vulnerability in PSM Plugins SupportCandy supportcandy allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects SupportCandy: from n/a through <= 3.4.4.

AI-Powered Analysis

AILast updated: 02/19/2026, 09:56:54 UTC

Technical Analysis

CVE-2026-25321 identifies a missing authorization vulnerability in the SupportCandy plugin developed by PSM Plugins, affecting all versions up to and including 3.4.4. SupportCandy is a WordPress-based customer support ticketing system widely used by organizations to manage customer inquiries and support workflows. The vulnerability arises from incorrectly configured access control security levels within the plugin, which fail to properly enforce authorization checks on certain operations. This misconfiguration can allow an attacker to perform unauthorized actions, potentially including viewing, modifying, or deleting support tickets or other sensitive data managed by the plugin. Although no exploits have been reported in the wild, the vulnerability is publicly disclosed and could be targeted by attackers seeking to leverage weak access controls. The lack of a CVSS score indicates that the vulnerability has not yet been fully assessed for severity, but the nature of missing authorization typically implies a significant risk. The issue affects the confidentiality and integrity of data handled by SupportCandy, and exploitation does not appear to require user interaction, increasing the threat level. No patches or fixes are currently linked, so organizations must monitor vendor communications for updates. The vulnerability was reserved and published in early 2026, indicating recent discovery and disclosure.

Potential Impact

For European organizations, the impact of CVE-2026-25321 can be substantial, especially for those relying on SupportCandy for customer support operations. Unauthorized access to support tickets could lead to exposure of sensitive customer information, including personal data protected under GDPR, resulting in compliance violations and potential fines. Integrity of support data could be compromised, undermining trust and operational effectiveness. Attackers exploiting this vulnerability might escalate privileges or pivot to other parts of the network if SupportCandy is integrated with broader IT infrastructure. The availability impact is likely limited but cannot be ruled out if attackers manipulate or delete critical support data. SMEs and enterprises in sectors with high customer interaction, such as retail, finance, and healthcare, are particularly at risk. The absence of known exploits provides a window for proactive defense, but the public disclosure increases the likelihood of future exploitation attempts. European organizations must consider the reputational and regulatory consequences of a breach stemming from this vulnerability.

Mitigation Recommendations

1. Monitor official PSM Plugins and SupportCandy channels for security patches addressing CVE-2026-25321 and apply updates immediately upon release. 2. Conduct a thorough audit of SupportCandy access control configurations to ensure that authorization checks are correctly enforced for all user roles and operations. 3. Implement strict role-based access controls (RBAC) within WordPress and SupportCandy to minimize privileges granted to users and plugins. 4. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious requests targeting SupportCandy endpoints. 5. Regularly review logs for unusual access patterns or unauthorized attempts to interact with the support system. 6. Isolate the SupportCandy plugin environment where possible, limiting its network exposure and integration with sensitive systems. 7. Educate IT and security teams about the vulnerability specifics to enhance incident detection and response readiness. 8. Consider alternative support platforms if timely patching or mitigation is not feasible, especially for high-risk environments.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2026-02-02T12:20:47.811Z
Cvss Version
null
State
PUBLISHED

Threat ID: 6996d0396aea4a407a4bdaac

Added to database: 2/19/2026, 8:56:25 AM

Last enriched: 2/19/2026, 9:56:54 AM

Last updated: 2/21/2026, 12:15:25 AM

Views: 2

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