p PatchFirst

PatchFirst · Vulnerabilidades recientes

Vulnerabilidades de tendenci

Vulnerabilidades publicadas para tendenci en los últimos 30 días: 0. Incluidas en el catálogo KEV: 0.

Filtrar vulnerabilidades
Borrar filtros

Vulnerabilidades: 5

  1. CVE-2025-70960

    Media · CVSS 5.4EPSS 0,27%Sin corrección publicada

    CVE-2025-70960

    A stored cross-site scripting (XSS) vulnerability in the Forums module of Tendenci CMS v15.3.7 allows attackers to execute arbitrary web scripts or HTML via injecting a crafted payload.

    Publicación Actualización
  2. CVE-2025-70959

    Media · CVSS 5.4EPSS 0,27%Sin corrección publicada

    CVE-2025-70959

    A stored cross-site scripting (XSS) vulnerability in the Jobs module of Tendenci CMS v15.3.7 allows attackers to execute arbitrary web scripts or HTML via injecting a crafted payload.

    Publicación Actualización
  3. CVE-2020-36962

    Media · CVSS 5.3EPSS 12,46%Corrección disponible

    Tendenci 12.3.1 - CSV/ Formula Injection

    Tendenci 12.3.1 contains a CSV formula injection vulnerability in the contact form message field that allows attackers to inject malicious formulas during export. Attackers can submit crafted payloads like '=10+20+cmd|' /C calc'!A0' in the message field to trigger arbitrary command execution when the CSV is opened in spreadsheet applications.

    • Actualiza a 12.3.2
    Publicación Actualización
  4. CVE-2026-23946

    Media · CVSS 6.8EPSS 0,84%Corrección disponible

    Tendenci has Authenticated Remote Code Execution via Pickle Deserialization

    Tendenci is an open source content management system built for non-profits, associations and cause-based sites. Versions 15.3.11 and below include a critical deserialization vulnerability in the Helpdesk module (which is not enabled by default). This vulnerability allows Remote Code Execution (RCE) by an authenticated user with staff security level due to using Python's pickle module in helpdesk /reports/. The original CVE-2020-14942 was incompletely patched. While ticket_list() was fixed to use safe JSON deserialization, the run_report() function still uses unsafe pickle.loads(). The impact is limited to the permissions of the user running t

    • Actualiza a 15.3.12
    Publicación Actualización

Comprueba tu servidor

Compara tu pila y las versiones instaladas con las bases actuales de vulnerabilidades.

Comprueba tu servidor →