Salvatore Bonaccorso pushed to branch master at Debian Security Tracker / 
security-tracker


Commits:
bb564d24 by security tracker role at 2025-07-10T08:12:12+00:00
automatic update

- - - - -


1 changed file:

- data/CVE/list


Changes:

=====================================
data/CVE/list
=====================================
@@ -1,3 +1,169 @@
+CVE-2025-7387 (The Lana Downloads Manager plugin for WordPress is vulnerable 
to Store ...)
+       TODO: check
+CVE-2025-6976 (The Events Manager \u2013 Calendar, Bookings, Tickets, and 
more! plugi ...)
+       TODO: check
+CVE-2025-6975 (The Events Manager \u2013 Calendar, Bookings, Tickets, and 
more! plugi ...)
+       TODO: check
+CVE-2025-6970 (The Events Manager \u2013 Calendar, Bookings, Tickets, and 
more! plugi ...)
+       TODO: check
+CVE-2025-6377 (A remote code execution security issue exists in the Rockwell 
Automati ...)
+       TODO: check
+CVE-2025-6376 (A remote code execution security issue exists in the Rockwell 
Automati ...)
+       TODO: check
+CVE-2025-6236 (The Hostel WordPress plugin before 1.1.5.9 does not sanitise 
and escap ...)
+       TODO: check
+CVE-2025-6234 (The Hostel WordPress plugin before 1.1.5.8 does not sanitise 
and escap ...)
+       TODO: check
+CVE-2025-5807 (The Gwolle Guestbook plugin for WordPress is vulnerable to 
Stored Cros ...)
+       TODO: check
+CVE-2025-53753
+       REJECTED
+CVE-2025-53752
+       REJECTED
+CVE-2025-53751
+       REJECTED
+CVE-2025-53750
+       REJECTED
+CVE-2025-53749
+       REJECTED
+CVE-2025-53748
+       REJECTED
+CVE-2025-53747
+       REJECTED
+CVE-2025-53746
+       REJECTED
+CVE-2025-53624 (The Docusaurus gists plugin adds a page to your Docusaurus 
instance, d ...)
+       TODO: check
+CVE-2025-4406 (The wpForo Forum plugin for WordPress is vulnerable to Stored 
Cross-Si ...)
+       TODO: check
+CVE-2025-46406 (A Privilege Context Switching Error (CWE-270) in the Command 
Center Se ...)
+       TODO: check
+CVE-2025-44003 (Missing Release of Resource after Effective Lifetime (CWE-772) 
in the  ...)
+       TODO: check
+CVE-2025-38319 (In the Linux kernel, the following vulnerability has been 
resolved:  d ...)
+       TODO: check
+CVE-2025-38318 (In the Linux kernel, the following vulnerability has been 
resolved:  p ...)
+       TODO: check
+CVE-2025-38317 (In the Linux kernel, the following vulnerability has been 
resolved:  w ...)
+       TODO: check
+CVE-2025-38316 (In the Linux kernel, the following vulnerability has been 
resolved:  w ...)
+       TODO: check
+CVE-2025-38315 (In the Linux kernel, the following vulnerability has been 
resolved:  B ...)
+       TODO: check
+CVE-2025-38314 (In the Linux kernel, the following vulnerability has been 
resolved:  v ...)
+       TODO: check
+CVE-2025-38313 (In the Linux kernel, the following vulnerability has been 
resolved:  b ...)
+       TODO: check
+CVE-2025-38312 (In the Linux kernel, the following vulnerability has been 
resolved:  f ...)
+       TODO: check
+CVE-2025-38311 (In the Linux kernel, the following vulnerability has been 
resolved:  i ...)
+       TODO: check
+CVE-2025-38310 (In the Linux kernel, the following vulnerability has been 
resolved:  s ...)
+       TODO: check
+CVE-2025-38309 (In the Linux kernel, the following vulnerability has been 
resolved:  d ...)
+       TODO: check
+CVE-2025-38308 (In the Linux kernel, the following vulnerability has been 
resolved:  A ...)
+       TODO: check
+CVE-2025-38307 (In the Linux kernel, the following vulnerability has been 
resolved:  A ...)
+       TODO: check
+CVE-2025-38306 (In the Linux kernel, the following vulnerability has been 
resolved:  f ...)
+       TODO: check
+CVE-2025-38305 (In the Linux kernel, the following vulnerability has been 
resolved:  p ...)
+       TODO: check
+CVE-2025-38304 (In the Linux kernel, the following vulnerability has been 
resolved:  B ...)
+       TODO: check
+CVE-2025-38303 (In the Linux kernel, the following vulnerability has been 
resolved:  B ...)
+       TODO: check
+CVE-2025-38302 (In the Linux kernel, the following vulnerability has been 
resolved:  b ...)
+       TODO: check
+CVE-2025-38301 (In the Linux kernel, the following vulnerability has been 
resolved:  n ...)
+       TODO: check
+CVE-2025-38300 (In the Linux kernel, the following vulnerability has been 
resolved:  c ...)
+       TODO: check
+CVE-2025-38299 (In the Linux kernel, the following vulnerability has been 
resolved:  A ...)
+       TODO: check
+CVE-2025-38298 (In the Linux kernel, the following vulnerability has been 
resolved:  E ...)
+       TODO: check
+CVE-2025-38297 (In the Linux kernel, the following vulnerability has been 
resolved:  P ...)
+       TODO: check
+CVE-2025-38296 (In the Linux kernel, the following vulnerability has been 
resolved:  A ...)
+       TODO: check
+CVE-2025-38295 (In the Linux kernel, the following vulnerability has been 
resolved:  p ...)
+       TODO: check
+CVE-2025-38294 (In the Linux kernel, the following vulnerability has been 
resolved:  w ...)
+       TODO: check
+CVE-2025-38293 (In the Linux kernel, the following vulnerability has been 
resolved:  w ...)
+       TODO: check
+CVE-2025-38292 (In the Linux kernel, the following vulnerability has been 
resolved:  w ...)
+       TODO: check
+CVE-2025-38291 (In the Linux kernel, the following vulnerability has been 
resolved:  w ...)
+       TODO: check
+CVE-2025-38290 (In the Linux kernel, the following vulnerability has been 
resolved:  w ...)
+       TODO: check
+CVE-2025-38289 (In the Linux kernel, the following vulnerability has been 
resolved:  s ...)
+       TODO: check
+CVE-2025-38288 (In the Linux kernel, the following vulnerability has been 
resolved:  s ...)
+       TODO: check
+CVE-2025-38287 (In the Linux kernel, the following vulnerability has been 
resolved:  I ...)
+       TODO: check
+CVE-2025-38286 (In the Linux kernel, the following vulnerability has been 
resolved:  p ...)
+       TODO: check
+CVE-2025-38285 (In the Linux kernel, the following vulnerability has been 
resolved:  b ...)
+       TODO: check
+CVE-2025-38284 (In the Linux kernel, the following vulnerability has been 
resolved:  w ...)
+       TODO: check
+CVE-2025-38283 (In the Linux kernel, the following vulnerability has been 
resolved:  h ...)
+       TODO: check
+CVE-2025-38282 (In the Linux kernel, the following vulnerability has been 
resolved:  k ...)
+       TODO: check
+CVE-2025-38281 (In the Linux kernel, the following vulnerability has been 
resolved:  w ...)
+       TODO: check
+CVE-2025-38280 (In the Linux kernel, the following vulnerability has been 
resolved:  b ...)
+       TODO: check
+CVE-2025-38279 (In the Linux kernel, the following vulnerability has been 
resolved:  b ...)
+       TODO: check
+CVE-2025-38278 (In the Linux kernel, the following vulnerability has been 
resolved:  o ...)
+       TODO: check
+CVE-2025-38277 (In the Linux kernel, the following vulnerability has been 
resolved:  m ...)
+       TODO: check
+CVE-2025-38276 (In the Linux kernel, the following vulnerability has been 
resolved:  f ...)
+       TODO: check
+CVE-2025-38275 (In the Linux kernel, the following vulnerability has been 
resolved:  p ...)
+       TODO: check
+CVE-2025-38274 (In the Linux kernel, the following vulnerability has been 
resolved:  f ...)
+       TODO: check
+CVE-2025-38273 (In the Linux kernel, the following vulnerability has been 
resolved:  n ...)
+       TODO: check
+CVE-2025-38272 (In the Linux kernel, the following vulnerability has been 
resolved:  n ...)
+       TODO: check
+CVE-2025-38271 (In the Linux kernel, the following vulnerability has been 
resolved:  n ...)
+       TODO: check
+CVE-2025-38270 (In the Linux kernel, the following vulnerability has been 
resolved:  n ...)
+       TODO: check
+CVE-2025-38269 (In the Linux kernel, the following vulnerability has been 
resolved:  b ...)
+       TODO: check
+CVE-2025-38268 (In the Linux kernel, the following vulnerability has been 
resolved:  u ...)
+       TODO: check
+CVE-2025-38267 (In the Linux kernel, the following vulnerability has been 
resolved:  r ...)
+       TODO: check
+CVE-2025-38266 (In the Linux kernel, the following vulnerability has been 
resolved:  p ...)
+       TODO: check
+CVE-2025-38265 (In the Linux kernel, the following vulnerability has been 
resolved:  s ...)
+       TODO: check
+CVE-2025-35983 (Improper Certificate Validation (CWE-295) in the Controller 
7000 OneLi ...)
+       TODO: check
+CVE-2025-0646
+       REJECTED
+CVE-2025-0141 (An incorrect privilege assignment vulnerability in the Palo 
Alto Netwo ...)
+       TODO: check
+CVE-2025-0140 (An incorrect privilege assignment vulnerability in the Palo 
Alto Netwo ...)
+       TODO: check
+CVE-2025-0139 (An incorrect privilege assignment vulnerability in Palo Alto 
Networks  ...)
+       TODO: check
+CVE-2024-10391
+       REJECTED
+CVE-2023-50458 (In Dradis before 4.11.0, the Output Console shows a job queue 
that may ...)
+       TODO: check
 CVE-2025-7370 [Null Pointer Dereference on libsoup through function 
"soup_cookie_jar_add_cookie" in soup-cookie-jar.c]
        - libsoup3 <unfixed> (unimportant)
        NOTE: https://gitlab.gnome.org/GNOME/libsoup/-/issues/430
@@ -2835,7 +3001,8 @@ CVE-2025-34078 (A local privilege escalation 
vulnerability exists in NSClient++
        NOT-FOR-US: NSClient++
 CVE-2025-34076 (An authenticated local file inclusion vulnerability exists in 
Microweb ...)
        NOT-FOR-US: microweber
-CVE-2025-34075 (An authenticated virtual machine escape vulnerability exists 
in HashiC ...)
+CVE-2025-34075
+       REJECTED
        TODO: check
 CVE-2025-34074 (An authenticated remote code execution vulnerability exists in 
Lucee\u ...)
        NOT-FOR-US: Lucee
@@ -5048,6 +5215,7 @@ CVE-2025-52938 (Out-of-bounds Read vulnerability in 
dail8859 NotepadNext (src/lu
 CVE-2025-52937 (Vulnerability in PointCloudLibrary PCL 
(surface/src/3rdparty/opennurbs ...)
        - pcl <not-affected> (PCL in Debian uses the system copy of zlib)
 CVE-2025-52936 (Improper Link Resolution Before File Access ('Link Following') 
vulnera ...)
+       {DLA-4238-1}
        - sslh <unfixed> (bug #1108284)
        NOTE: https://github.com/yrutschle/sslh/pull/494
        NOTE: Fixed by: 
https://github.com/yrutschle/sslh/commit/0fe9bd5a956a123342ff12352b25bff8025dac69
 (v2.2.2)



View it on GitLab: 
https://salsa.debian.org/security-tracker-team/security-tracker/-/commit/bb564d2469ccdec299e82a1759c1d91826dddd9e

-- 
View it on GitLab: 
https://salsa.debian.org/security-tracker-team/security-tracker/-/commit/bb564d2469ccdec299e82a1759c1d91826dddd9e
You're receiving this email because of your account on salsa.debian.org.


_______________________________________________
debian-security-tracker-commits mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-security-tracker-commits

Reply via email to