p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in juzaweb/cms

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für juzaweb/cms: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 5

  1. CVE-2025-6736

    Mittel · CVSS 5.3EPSS 0,49%Keine Korrektur veröffentlicht

    juzaweb CMS Add New Themes Page install improper authorization

    A vulnerability classified as critical was found in juzaweb CMS 3.4.2. Affected by this vulnerability is an unknown functionality of the file /admin-cp/theme/install of the component Add New Themes Page. The manipulation leads to improper authorization. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

    Veröffentlicht Aktualisiert
  2. CVE-2025-6735

    Mittel · CVSS 5.3EPSS 0,5%Keine Korrektur veröffentlicht

    juzaweb CMS Import Page imports improper authorization

    A vulnerability classified as critical has been found in juzaweb CMS 3.4.2. Affected is an unknown function of the file /admin-cp/imports of the component Import Page. The manipulation leads to improper authorization. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

    Veröffentlicht Aktualisiert
  3. CVE-2025-5420

    Mittel · CVSS 5.1EPSS 0,38%Keine Korrektur veröffentlicht

    juzaweb CMS Profile Page upload cross site scripting

    A vulnerability classified as problematic was found in juzaweb CMS up to 3.4.2. Affected by this vulnerability is an unknown functionality of the file /admin-cp/file-manager/upload of the component Profile Page. The manipulation of the argument Upload leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →