| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| In JetBrains YouTrack before 2026.2.19840 private issue summaries and descriptions could be read via agile board queries for archived projects |
| Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in InstaWP InstaWP Connect instawp-connect allows Blind SQL Injection.This issue affects InstaWP Connect: from n/a through 0.1.4.4. |
| The Photo Gallery, Sliders, Proofing and Themes – NextGEN Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 4.5.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the plugin's "What must the lightbox be applied to?" setting (thumbEffectContext) to be configured as "Try to apply to all images" or "Try to apply to all images that link to image files," which is not the shipping default, and also requires the attacker's comment to reach a publicly rendered state. |
| The Pie Register – User Registration, Profiles & Content Restriction plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.8.4.17 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to overwrite the role of the site's primary administrator account (user ID 1) with the registration form's configured role, demoting the administrator to a lower-privileged role and locking them out of wp-admin. This vulnerability is exploitable only on PHP 8+, where casting a WP_Error object to int yields 1, causing the role modification to target user ID 1. |
| Confused deputy in DevTools in Google Chrome prior to 158.0.8127.36 allowed a remote attacker leveraging social engineering to bypass web origin policy via a crafted HTML page. (Chromium security severity: Low) |
| In JetBrains TeamCity before 2026.2.2 stored XSS in GitHub issue tracker suggestions was possible |
| Incomplete cleanup in Navigation in Google Chrome on on iOS prior to 158.0.8127.36 allowed a remote attacker to potentially bypass web origin policy via a crafted HTML page. (Chromium security severity: Medium) |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via a URL stream handler in the Kotlin DSL sandbox |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 the TFS helper process exposed an unauthenticated command server |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Git submodule URLs |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS on the Projects Import page was possible |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 hTML injection in pipeline notification emails was possible via commit messages |
| In JetBrains TeamCity before 2026.2.2 the current request details debug endpoint exposed authentication headers and session cookies |
| In JetBrains Datalore before 2026.4.1 improper authorization allowed notebook viewers to read attached environment variable values |
| In JetBrains Datalore before 2026.4.1 open redirect after OpenID login was possible via the origin parameter |
| In JetBrains YouTrack before 2026.2.19840 the attachment upload size limit could be bypassed via the REST API |
| In JetBrains YouTrack before 2026.2.19728 missing authorization allowed creating sub-articles without the Create Article permission |
| A vulnerability in the Audio, Web, and Video Conferencing (AWV) component of Mitel MiCollab through 10.3 (10.3.0.18) could allow an unauthenticated attacker to conduct an arbitrary file upload attack due to insufficient file type validation. A successful exploit could allow an attacker to upload arbitrary files to the target system. This is MTLVULN-1861. |
| In the Linux kernel, the following vulnerability has been resolved:
mm/gup: fix clearing folios in memfd_pin_folios()
memfd_pin_folios() pins folios obtained directly from the page cache
without checking whether they are uptodate. However, shmem fallocate()
can leave newly allocated folios uncleared and not uptodate. Callers
such as udmabuf can then expose uninitialized memory to userspace.
Clear non-uptodate folios and mark them uptodate under the folio lock
before returning them to the caller.
Fix generated by an LLM and sent by Chris Mason in private.
[ david: simplify description and comment ] |
| In the Linux kernel, the following vulnerability has been resolved:
ptp: fix use-after-free in extts_fifo_show() reading tsevqs unlocked
extts_fifo_show() walks ptp->tsevqs with list_count_nodes() and then
list_first_entry() without holding ptp->tsevqs_lock, the spinlock that
"protects tsevqs from concurrent access". Every other accessor of the
list honours it: ptp_open() (list_add_tail), ptp_release() (list_del
followed by kfree of the per-fd queue), ptp_clock_release() and
ptp_clock_event() all take tsevqs_lock. extts_fifo_show() is the only
one that does not.
A per-fd timestamp queue is appended to tsevqs on open("/dev/ptpN") and
removed and freed on close(), both under tsevqs_lock:
scoped_guard(spinlock_irq, &ptp->tsevqs_lock)
list_del(&queue->qlist);
bitmap_free(queue->mask);
kfree(queue);
So a read of /sys/class/ptp/ptpN/fifo running concurrently with a
close() of a /dev/ptpN fd can have list_count_nodes() walk into the
queue that close() is removing and freeing, dereferencing freed memory
(use-after-free) or a poisoned list pointer.
Take tsevqs_lock around the list walk. The fifo only ever draws from the
first queue, which is the registration-time queue created in
ptp_clock_register() and freed only in ptp_clock_release(); that cannot
run while the sysfs attribute is being read, so the dequeue from
queue->buf under queue->lock may stay outside tsevqs_lock and the lock
order is unchanged. |