Security readout for executives and security teams
Plain-English summary
CVE-2026-1251 affects the WordPress SupportCandy helpdesk plugin through version 3.4.4. A logged-in user with subscriber-level access could take attachments from other users’ tickets by abusing weak ownership checks. Business risk is unauthorized exposure or disruption of customer support files, especially where ticket attachments contain personal, financial, or operational data.
Executive priority
Treat as a near-term remediation item for customer-facing WordPress support portals. It is not rated critical, but the data exposure path affects customer attachments and only requires a low-privilege account. Prioritize environments handling sensitive support files or allowing self-service user registration.
Technical view
The flaw is an insecure direct object reference in SupportCandy’s add_reply function. Missing validation on a user-controlled attachment key allows an authenticated subscriber-or-higher attacker to reference arbitrary attachment IDs through description_attachments, re-associate files to their own tickets, and remove access from the original owners. CVSS is 5.4, with low attack complexity and required authentication.
Likely exposure
Exposure is limited to WordPress sites running SupportCandy up to and including 3.4.4, where untrusted or broadly available user accounts exist. Sites allowing customer registration, external portal access, or many subscriber-level users have higher practical risk.
Exploitation context
The provided sources do not show active exploitation, and this CVE is not listed as KEV in the supplied data. Exploitation requires authentication but no user interaction, making misuse plausible if an attacker can obtain or create a low-privilege account.
Researcher notes
The public record identifies CWE-639 and references the vulnerable code path plus WordPress Trac changeset 3448376. The supplied data does not name a fixed plugin version. Avoid assuming exploit availability or remediation details beyond vendor and Trac evidence.
Mitigation direction
- Inventory all WordPress sites using the SupportCandy plugin.
- Identify installations running SupportCandy 3.4.4 or earlier.
- Check vendor guidance and release notes for the patched version.
- Apply the vendor-supported update when confirmed available.
- Restrict subscriber-level access where it is not business-required.
- Review ticket attachments for sensitive data exposure.
Validation and detection
- Confirm installed SupportCandy versions across WordPress environments.
- Flag any instance at version 3.4.4 or earlier.
- Review user roles with subscriber-level access or higher.
- Check whether public account registration is enabled.
- Review support ticket attachment access and ownership logs.
- Verify remediation against vendor release notes or Trac changeset.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-1251 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/89df3005-0967-474f-8a4e-3b23273dd1a2?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/supportcandy/trunk/includes/admin/tickets/class-wpsc-individual-ticket.php#L1603CVE reference
- https://plugins.trac.wordpress.org/changeset/3448376/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.