CVE-2026-25321
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMissing 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a Missing Authorization (CWE-862) vulnerability in the SupportCandy WordPress plugin where incorrectly configured access control security levels allow authenticated users to access functionality or data beyond their intended permissions. The CVSS 5.3 indicates that some form of authentication exists but authorization checks are insufficient or missing in certain code paths, potentially allowing privilege escalation or unauthorized access to support ticket management features.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm SupportCandy installation and versionIn WordPress admin, go to Plugins > Installed Plugins and locate SupportCandy. Note the version number displayed. Alternatively, check the plugin header in wp-content/plugins/supportcandy/support-candy.php for the 'Version' field.Affected if SupportCandy is installed with any version prior to the patched release; the specific vulnerable versions depend on when the vendor released the fix.
-
Review SupportCandy user roles and capabilitiesGo to SupportCandy > Settings > Roles and Capabilities (or similar access control settings page). List all defined roles and the permissions assigned to each (e.g., create ticket, view all tickets, delete ticket). Identify which roles have elevated permissions.Affected if Any authenticated user role (e.g., subscriber, customer) is assigned capabilities that should be restricted to higher-privilege roles like agent or administrator.
-
Inspect admin AJAX handlers for missing capability checksExamine PHP files in the plugin directory, particularly those handling admin-ajax.php requests (typically in includes/ajax/ or similar paths). Search for AJAX action handlers and verify if they include current_user_can() or similar capability checks before executing sensitive operations.Affected if AJAX handlers exist that perform privileged operations (ticket modification, user role changes, data export) without calling current_user_can() or equivalent authorization validation.
-
Check frontend form handlers for authorizationReview PHP files handling frontend ticket submission and management forms. Look for functions processing $_POST or $_GET parameters related to ticket operations (create, update, delete, view). Verify each handler validates user authorization before modifying ticket data.Affected if Frontend form handlers process ticket actions without verifying the current user has permission to perform that specific operation on the target ticket.
-
Audit WordPress capability mapping in plugin settingsNavigate to SupportCandy > Settings > Permissions or similar section. Compare the capability requirements configured for each action against the actual checks performed in the plugin code. Look for discrepancies between configured permissions and enforced permissions.Affected if The plugin settings define one set of access rules, but the underlying code does not enforce those rules consistently across all code paths.
A user is affected if SupportCandy is installed and any AJAX handler, frontend form, or sensitive operation lacks proper capability checks (current_user_can()) or nonce verification, allowing authenticated users to perform actions beyond their assigned role permissions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate SupportCandy to the latest version which should include proper capability checks and authorization validation for all sensitive operations. If no update is available, manually review and add WordPress capability checks (current_user_can()) and nonce verification to all admin AJAX handlers and frontend forms.
Latest version of SupportCandy (newer than 3.4.4)
- 1. Log in to your WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate SupportCandy in the plugin list
- 4. If an update is available, click 'Update Now' to install the latest version
- 5. After updating, verify the plugin is running on a version newer than 3.4.4
- 6. Test that the authorization controls are functioning correctly for all user roles
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25321 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-25321 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data