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

CVE-2026-1251

MEDIUM · 5.4 CVSS v3.1 Published 2026-01-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
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.

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 · high confidence

The SupportCandy WordPress plugin has an IDOR vulnerability in the add_reply function where the description_attachments parameter accepts arbitrary attachment IDs without validating ownership. Authenticated users with subscriber-level access can specify attachment IDs belonging to other users' tickets, reassigning those files to their own tickets and breaking the original owner's access.

MitigationUpdate to plugin version 3.4.5 or later which implements proper validation on attachment IDs to ensure users can only access their own file attachments. Until patched, restrict user permissions to the minimum required and monitor for suspicious ticket activity.

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 checks

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

  1. Verify SupportCandy plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for SupportCandy in the list. Note the installed version displayed.
    Affected if SupportCandy plugin is active and installed with a version earlier than 3.4.5
  2. Confirm the plugin version
    Compare the installed version number against the fixed version 3.4.5. The version is visible on the plugins page or in the plugin's main PHP file header.
    Affected if The installed version is below 3.4.5 (e.g., 3.4.4, 3.4.3, earlier)
  3. Check if ticket creation and reply features are enabled
    Navigate to SupportCandy settings in WordPress admin. Look for settings related to ticket creation, replies, and file attachments. Verify the Allow attachments option is enabled.
    Affected if Ticket replies and file attachments are enabled, allowing users to use the add_reply function with the vulnerable description_attachments parameter
  4. Verify subscriber-level users exist and can access tickets
    In WordPress admin, go to Users > All Users and check for users with the Subscriber role. Also check SupportCandy settings for any role-based access controls that allow subscribers to create tickets or reply to tickets.
    Affected if Subscriber-level accounts exist and are permitted to create tickets or submit replies, enabling them to reach the vulnerable add_reply function

Your environment is affected if SupportCandy plugin version is below 3.4.5, the ticket reply and attachment features are active, and subscriber-level users have access to submit replies with attachments.

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 to plugin version 3.4.5 or later which implements proper validation on attachment IDs to ensure users can only access their own file attachments. Until patched, restrict user permissions to the minimum required and monitor for suspicious ticket activity.

Recommended fix Moderate confidence

3.4.5 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find SupportCandy – Helpdesk & Customer Support Ticket System
  4. If an update is available, click 'Update Now' to update to the latest version
  5. Alternatively, go to Dashboard > Updates and click 'Update Plugins'
  6. Verify the plugin updated successfully by checking the version number

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1251 — 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-1251 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