dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-54826

HIGH · 7.6 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable Zero-click 8 weeks old

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 · unedited
Subscriber Insecure Direct Object References (IDOR) in SupportCandy <= 3.4.6 versions.

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 confidence

An IDOR vulnerability in SupportCandy WordPress plugin versions 3.4.6 and below allows authenticated users with Subscriber role to access or modify resources (likely tickets or customer data) that should require higher privileges. The application fails to properly validate object-level authorization on direct object references.

MitigationUpdate SupportCandy to a version higher than 3.4.6 when available, or implement role-based access control enforcement at the object level until the patch is applied.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SupportCandy plugin is installed
    Navigate to WordPress admin > Plugins and locate SupportCandy in the list of installed plugins, or check the /wp-content/plugins/ directory for the supportcandy folder
    Affected if SupportCandy plugin is present in the WordPress installation
  2. Identify installed SupportCandy version
    In WordPress admin > Plugins > Installed Plugins, find SupportCandy and note the version number displayed under the plugin name. Alternatively, check the main plugin file (supportcandy.php) for the 'Version' header in the plugin metadata
    Affected if The version listed is 3.4.6 or lower
  3. Check for Subscriber role users
    Navigate to WordPress admin > Users and review the list for any accounts assigned the Subscriber role, or use WP-CLI: wp user list --role=subscriber
    Affected if At least one user account with Subscriber role exists in the system
  4. Verify ticket or customer data access is not properly restricted
    As a Subscriber-level user, attempt to access SupportCandy ticket URLs or API endpoints directly (such as /wp-admin/admin.php?page=wpsc-tickets or associated REST API routes) to see if unauthorized ticket data or customer information is returned
    Affected if A Subscriber role user can view, modify, or delete tickets or customer data that were created by administrators or other higher-privileged roles

The environment is affected if SupportCandy version 3.4.6 or lower is installed AND at least one Subscriber role user exists AND that user can access resources requiring higher privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update SupportCandy to a version higher than 3.4.6 when available, or implement role-based access control enforcement at the object level until the patch is applied.

Recommended fix Moderate confidence

SupportCandy latest version (verify version > 3.4.6 on WordPress plugin repository)

  1. Check if your WordPress site uses the SupportCandy plugin
  2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. Locate SupportCandy and note the current version number
  4. If version is 3.4.6 or below, update to the latest available version from the WordPress plugin repository
  5. After updating, verify the fix by testing subscriber-level access controls

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54826 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-54826 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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