-
CVE-2026-23898
•
published on April 1, 2026
Lack of input validation leads to an arbitrary file deletion vulnerability in the autoupdate server mechanism.
-
CVE-2026-23898
•
published on April 1, 2026
Lack of input validation leads to an arbitrary file deletion vulnerability in the autoupdate server mechanism.
-
CVE-2026-23898
•
published on April 1, 2026
Lack of input validation leads to an arbitrary file deletion vulnerability in the autoupdate server mechanism.
-
CVE-2026-23898
•
published on April 1, 2026
Lack of input validation leads to an arbitrary file deletion vulnerability in the autoupdate server mechanism.
-
CVE-2026-23898
•
published on April 1, 2026
Lack of input validation leads to an arbitrary file deletion vulnerability in the autoupdate server mechanism.
-
CVE-2026-23898
•
published on April 1, 2026
Lack of input validation leads to an arbitrary file deletion vulnerability in the autoupdate server mechanism.
-
CVE-2026-23898
•
published on April 1, 2026
Lack of input validation leads to an arbitrary file deletion vulnerability in the autoupdate server mechanism.
-
CVE-2026-23898
•
published on April 1, 2026
Lack of input validation leads to an arbitrary file deletion vulnerability in the autoupdate server mechanism.
-
CVE-2026-23898
•
published on April 1, 2026
Lack of input validation leads to an arbitrary file deletion vulnerability in the autoupdate server mechanism.
-
CVE-2026-23898
•
published on April 1, 2026
Lack of input validation leads to an arbitrary file deletion vulnerability in the autoupdate server mechanism.
-
CVE-2026-23898
•
published on April 1, 2026
Lack of input validation leads to an arbitrary file deletion vulnerability in the autoupdate server mechanism.
-
CVE-2026-21629
•
published on April 1, 2026
The ajax component was excluded from the default logged-in-user check in the administrative area. This behavior was potentially unexpected by 3rd party developers.
-
CVE-2026-21629
•
published on April 1, 2026
The ajax component was excluded from the default logged-in-user check in the administrative area. This behavior was potentially unexpected by 3rd party developers.
-
CVE-2026-21629
•
published on April 1, 2026
The ajax component was excluded from the default logged-in-user check in the administrative area. This behavior was potentially unexpected by 3rd party developers.
-
CVE-2026-21629
•
published on April 1, 2026
The ajax component was excluded from the default logged-in-user check in the administrative area. This behavior was potentially unexpected by 3rd party developers.
-
CVE-2026-21629
•
published on April 1, 2026
The ajax component was excluded from the default logged-in-user check in the administrative area. This behavior was potentially unexpected by 3rd party developers.
-
CVE-2026-21629
•
published on April 1, 2026
The ajax component was excluded from the default logged-in-user check in the administrative area. This behavior was potentially unexpected by 3rd party developers.
-
CVE-2026-21629
•
published on April 1, 2026
The ajax component was excluded from the default logged-in-user check in the administrative area. This behavior was potentially unexpected by 3rd party developers.
-
CVE-2026-21629
•
published on April 1, 2026
The ajax component was excluded from the default logged-in-user check in the administrative area. This behavior was potentially unexpected by 3rd party developers.
-
CVE-2026-21629
•
published on April 1, 2026
The ajax component was excluded from the default logged-in-user check in the administrative area. This behavior was potentially unexpected by 3rd party developers.
