Security readout for executives and security teams
Plain-English summary
Tendenci sites running version 15.3.11 or earlier may allow a trusted staff user to trigger server-side code execution through the Helpdesk reporting feature. The Helpdesk module is reportedly not enabled by default, and exploitation requires authenticated staff-level access and user interaction. The vendor fixed the issue in 15.3.12.
Executive priority
Treat as a priority for organizations using Tendenci Helpdesk, especially public-facing community or association sites. The required staff privileges reduce likelihood, but successful exploitation could compromise confidentiality, integrity, and availability within the web application context.
Technical view
CVE-2026-23946 is an authenticated RCE in Tendenci Helpdesk /reports/ caused by unsafe Python pickle deserialization in run_report(). The earlier CVE-2020-14942 fix replaced unsafe deserialization in ticket_list(), but left run_report() using pickle.loads(). Impact is limited to the application user, typically www-data, according to the advisory.
Likely exposure
Exposure is limited to Tendenci deployments below 15.3.12 where the Helpdesk module is enabled and staff-level authenticated users can access reporting functionality.
Exploitation context
No active exploitation is indicated in the provided sources, and the CVE is not listed as KEV. The attack requires network access, high privileges, and user interaction per the CVSS vector, reducing broad internet-scale risk.
Researcher notes
Focus validation on Tendenci versions below 15.3.12 and Helpdesk reporting paths. The root issue is incomplete remediation of unsafe pickle deserialization. Avoid assuming impact beyond the application user permissions described by the advisory unless confirmed in the target environment.
Mitigation direction
- Upgrade Tendenci to version 15.3.12 or later.
- If upgrade is delayed, review vendor guidance for temporary controls.
- Disable the Helpdesk module if it is not business-critical.
- Restrict staff-level accounts to trusted users only.
- Review upload directory permissions and application user privileges.
Validation and detection
- Inventory Tendenci instances and confirm installed versions.
- Check whether the Helpdesk module is enabled.
- Verify staff users with access to Helpdesk reports.
- Confirm version 15.3.12 is deployed after remediation.
- Review application logs for unusual Helpdesk report activity.
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-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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 lookupCWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-23946 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
- 6.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
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:H/UI:R/S:U/C:H/I:H/A:H0.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.8MediumVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/tendenci/tendenci/security/advisories/GHSA-339m-4qw5-j2g3CVE reference · x_refsource_CONFIRM
- https://github.com/tendenci/tendenci/issues/867CVE reference · x_refsource_MISC
- https://github.com/tendenci/tendenci/commit/23d9fd85ab7654e9c83cfc86cb4175c0bd7a77f1CVE reference · x_refsource_MISC
- https://github.com/tendenci/tendenci/commit/2ff0a457614944a1b417081c543ea4c5bb95d636CVE reference · x_refsource_MISC
- https://github.com/tendenci/tendenci/commit/63e1b84a5b163466d1d8d811d35e7021a7ca0d0eCVE reference · x_refsource_MISC
- https://docs.python.org/3/library/pickle.html#restricting-globalsCVE reference · x_refsource_MISC
- https://github.com/advisories/GHSA-jqmc-fxxp-r589CVE reference · x_refsource_MISC
- https://github.com/tendenci/tendenci/releases/tag/v15.3.12CVE reference · x_refsource_MISC
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.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.