Corrupted packetized telemetry can be emitted by NASA's F´ (F Prime) flight and embedded software framework before version 4.3.0, because the Svc::TlmPacketizer component copies an incoming telemetry value into a fixed per-channel slot without verifying that the serialized value actually fits, allowing the copy to overrun adjacent channel fields inside the outgoing packet. The issue is rated CVSS 6.5 (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N), meaning unauthenticated attackers with adjacent-network reach to the telemetry path, plus influence over a telemetry source feeding a already-configured channel, can corrupt packetized telemetry; there is no code execution, data disclosure, or guaranteed crash, and no public exploit code has been identified at time of analysis. The vendor fixed the flaw in version 4.3.0.
Path traversal in FileRise 3.22.0 allows an authenticated non-administrator whose session holds inherited edit permission on a legitimate ancestor folder to supply dot and dot-dot segments through the /api/file/saveFile.php folder input, causing attacker-controlled files to be written outside the authorized folder and, where backend credentials permit, outside the configured WebDAV root. Exploitation requires a valid CSRF token plus an authenticated session with inherited edit rights (CVSS 3.1: 6.5, AV:N/AC:L/PR:L/UI:N, I:H only), and no public exploit identified at time of analysis; this is a moderate, authentication-gated integrity risk rather than a top-tier emergency. Vendor-released patch: 3.23.0.
Cross-project information disclosure in Plane (open-source project management tool) before version 1.4.0 lets an authenticated member of one project read the description_html of public page versions belonging to a different project within the same workspace. The PageVersionEndpoint resolves page versions by workspace and page_id only, so supplying another project's identifier in the URL bypasses the intended project boundary - the check that the caller belongs to the URL project passes, but the object lookup ignores that project. The issue is read-only (no cross-project modification), requires active membership in at least one project of the target workspace and knowledge of the target page_id, and no public exploit code has been identified at time of analysis.
Authenticated FileRise users who hold both upload and archive-extraction permissions can bypass the application's blocked-extension upload policy by packaging a PHP-family file inside a ZIP archive and extracting it, because the filename policy is never applied before ZipArchive::extractTo() writes entries to disk (CWE-434). All FileRise versions prior to 3.16.0 are affected via the network with low privileges (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N, 6.5); the guaranteed outcome is arbitrary-extension file write, and code execution occurs only on deployments whose web server actually executes content from the upload/storage directory. Exploitation is conditional rather than confirmed in the wild - no public exploit code has been identified at time of analysis and there is no CISA KEV entry - and the vendor addressed the flaw with upstream fix commit f7114ca2a4e624238dda0d097a07ad6b05c11bb6, released in version 3.16.0.
Missing object-level authorization in Plane 1.3.1 and earlier lets any authenticated project guest or member deactivate other project members - including administrators - by sending a PATCH that includes is_active while omitting the role field, and separately allows cross-member tampering with ProjectMemberPreference records via a trusted member_id path parameter. Exploitation requires a valid low-privilege account already enrolled in the target project (CVSS PR:L, network reachable, no user interaction), and results in high integrity impact with no confidentiality or availability loss scored; no public exploit code has been identified at time of analysis and the issue is not in CISA KEV. The flaw is fixed in Plane 1.4.0.
Missing authorization checks (CWE-862) in the Magepeople Inc. 'Bus Ticket Booking with Seat Reservation' WordPress plugin, affecting all versions through 5.9.7, let a request reach plugin endpoints that were never gated behind a proper capability or permission check, allowing manipulation or disruption of booking and reservation data. The issue is rated medium severity at CVSS 6.5, with the CVSS impact limited to partial integrity and availability and no confidentiality loss, so realistic damage is tampering with or denial of booking/reservation functionality rather than full site takeover. No public exploit code and no CISA KEV entry were identified at time of analysis, and no vendor-released fixed version is identified in the supplied data; exposure requires the plugin to be installed and active on a WordPress site.
FileRise versions prior to 3.23.0 allow an authenticated user who already holds a valid session and that session's CSRF token to change second-factor settings at the TOTP management endpoints without any recent full reauthentication, so the attacker can either disable an already-configured TOTP factor or activate a newly enrolled TOTP secret on an account that currently has none. The rated impact is integrity-only (CVSS 6.5, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N; CWE-306) because the enrollment endpoint returns HTTP 409 rather than overwriting an active authenticator, meaning a protected account can be weakened but not silently re-enrolled. The practical precondition is substantial - the attacker must already control an authenticated session plus its CSRF token - and no public exploit identified at time of analysis; the fix is shipped in 3.23.0.
Unauthenticated remote attackers can abuse a missing authorization check (CWE-862) in the WordPress plugin Push Notification for Post and BuddyPress to reach plugin functionality that should be access-controlled, affecting all releases from the initial version through 3.23. The assessed CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N scores 6.5, meaning any exposed site running this niche plugin can be probed by network attackers with no credentials, no user interaction, and no special configuration, but impact stays at low-level data disclosure and modification rather than full site compromise. No public exploit identified at time of analysis; the main exposure limiter is deployment, since only sites with the plugin installed and active are reachable.
Stored cross-site scripting in the WP w3all phpBB integration plugin (wp-w3all-phpbb-integration, versions through 3.1.0) lets an authenticated low-privileged user plant script content that is persisted server-side and later executed in the browser of any user who views the rendered page, rated CVSS 3.1 base 6.5 (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L). Exploitation requires a valid account on the WordPress site (at least low privileges per PR:L) plus a second user who loads the affected content (UI:R), and it presupposes the plugin is installed and active - a niche integration deployment that narrows the realistic target set. Reported by Patchstack; no public exploit code has been identified and the issue is not listed as confirmed actively exploited (CISA KEV) at time of analysis.
An out-of-bounds write in the DPDK lib/vhost vhost-crypto backend lets a guest VM that is authorized to issue vhost-crypto requests corrupt host memory by supplying an avail-ring descriptor index that the backend uses without validating it against the ring size. The affected code ships in Red Hat Fast Datapath packages for RHEL 8, 9, and 10 and is therefore inherited by related RHEL, Red Hat OpenShift Container Platform 4, and Red Hat OpenStack Platform 13 (Queens) deployments that consume those DPDK builds. Exploitation is restricted to hosts where the vhost-crypto backend is actually enabled and a virtio-crypto device is exposed to a guest (CVSS 6.5, AV:L/PR:L/S:C), and the assessed outcome is host datapath denial of service rather than data disclosure or modification; no public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV.
Host-side denial of service and potential memory corruption in DPDK's lib/vhost arise because memory-region sizes are not adequately validated before mmap during vhost memory-region setup (CWE-770). The affected code ships to customers through Red Hat Fast Datapath for RHEL 8, 9 and 10, and therefore reaches Red Hat Enterprise Linux 8/9/10, Red Hat OpenShift Container Platform 4 and Red Hat OpenStack Platform 13 (Queens) deployments that use DPDK vhost-user acceleration. An attacker who controls a connected vhost-user frontend - typically a guest VM or a process holding the vhost-user socket - can crash the host (CVSS 6.5, AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H); no public exploit code has been identified at time of analysis and there is no confirmation of active exploitation.
An infinite cleanup loop in DPDK's vhost-crypto library can be triggered by a local attacker with guest-level access via a crafted writeback descriptor chain, causing a denial of service (host/service hang). The vulnerability is rated CVSS 6.5 (Medium) with a local attack vector (AV:L), low complexity, and scope change; it only affects deployments where vhost-crypto is exposed as a virtio-crypto device backend to untrusted guests. No public exploit code or active exploitation has been identified at time of analysis.
An out-of-bounds write in the DPDK vhost-crypto backend allows a guest VM to overflow a host-side buffer and crash the host data plane. The flaw combines an integer overflow in the chain-length validation logic with missing length checks on the RSA request path, so crafted virtio-crypto descriptors can bypass size validation and corrupt host memory. Exposure is confined to hosts that have explicitly enabled the vhost-crypto (virtio-crypto) backend, exploitation requires low-privileged access from within a guest, and no public exploit code has been identified at time of analysis, with no confirmed active exploitation (CISA KEV).
Stack and heap buffer overflow in DPDK's nfp vDPA driver for Netronome/Corigine NFP SmartNICs allows a malicious guest VM with control of the virtqueue to corrupt host memory, leading to high integrity and availability impact and low confidentiality impact. The vulnerability is only exploitable when the host runs DPDK with the nfp vDPA driver active on NFP SmartNIC hardware, and the attacker must be positioned as a local guest able to drive the guest-side virtqueue. No public exploit code has been identified at time of analysis, and the vendor-rated CVSS 3.1 score is 6.5 (Medium); however, our independent assessment assigns a higher impact vector of AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H.
Use-after-free and type confusion in DPDK's vhost-crypto session handling allow a local attacker, such as a malicious guest VM or a low-privileged local process, to cause a denial of service on the host DPDK process. The vulnerability requires the host to run DPDK with the vhost-crypto library enabled and exposed to guests; it is scored CVSS 3.1 6.5 (Medium) with vector AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H. No public exploit identified at time of analysis.
Guest-to-host denial of service in the DPDK vhost library (lib/vhost) allows a malicious or misbehaving guest to underflow the copy length in the vhost enqueue path by supplying runt RX descriptors, which can stall or crash a shared host-side vhost backend such as OVS-DPDK. The flaw is rated CVSS 6.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H, mapped to CWE-191) and is only reachable by an attacker who already controls a guest VM (local-to-host scope, PR:L) - not by a remote unauthenticated network attacker - with impact limited to availability (no confidentiality or integrity effect). No public exploit was identified at time of analysis and there is no CISA KEV listing for this CVE; no vendor-released patch was identified at the time of analysis.
Denial of service in Nezha Monitoring 2.2.7 through 2.2.10 lets an authenticated RoleMember crash the whole dashboard process by racing their own agent's TCP/ICMP result report against deletion of a service the member owns, producing a nil pointer dereference in ServiceSentinel.worker that panics the process and takes down every tenant's web interface, REST API, and agent connections until the service is restarted. Confirmed actively exploited? No - no public exploit code or active exploitation has been identified at time of analysis, and the issue is availability-only (C:N/I:N/A:H) with no data disclosure or modification. The published CVSS of 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) matches the assessed impact, but independent analysis rates attack complexity as High (AC:H) because the attacker must win a concurrency window between the ownership check and the pointer dereference; that window is retriable, so practical reliability is higher than a one-shot race would suggest.
Missing authorization in the miniOrange WP OAuth Server WordPress plugin (all versions through 6.4.0) allows remote unauthenticated attackers to invoke plugin functionality that should have been gated behind capability or permission checks, resulting in low integrity and availability impact (CVSS 6.5, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L). Per the assessed vector, no authentication, privileges, or user interaction are required, so any WordPress site with this plugin active and reachable is potentially exposed; confidentiality impact is rated as none. There is no public exploit identified at time of analysis and no CISA KEV listing, and the available data does not identify a vendor-released patched version.
Stored cross-site scripting in the Meow Lightbox WordPress plugin (all versions up to and including 5.6.2) allows an authenticated subscriber-level user to inject arbitrary script through the 'display_name + comment' parameter, which then executes in the browser of any user viewing the injected page. Real-world risk is substantially lower than the 6.4 headline score suggests because three preconditions must all be met: the plugin's Output Buffering option must be explicitly enabled (it is disabled by default), the attacker must already have at least one approved comment on the site so that WordPress core auto-approves subsequent submissions, and any authenticated account (PR:L) is required - making default installations non-exploitable. No public exploit code or confirmed active exploitation has been identified at time of analysis, and no EPSS or CISA KEV signal is present in the available intelligence.
Stored cross-site scripting in the Mang Board plugin for WordPress (all versions up to and including 2.4.3) allows an authenticated user holding 'custom-level' access or above to inject arbitrary JavaScript through the 'content' parameter, which is then rendered without adequate sanitization or output escaping. The injected script is stored server-side and executes in the browser session of any user or administrator who later views the affected page, which is why the CVSS vector scores a scope change (S:C) with low confidentiality and integrity impact (6.4 overall). Exploitation requires a valid low-privileged account on a site that grants custom-level roles, and no public exploit code was identified at time of analysis; this is not listed on CISA KEV and should be handled as a routine patch-management item rather than an emergency.
Stored cross-site scripting in the GeoDirectory - WP Business Directory Plugin and Classified Listings Directory for WordPress (all versions up to and including 2.8.190) lets an authenticated attacker with subscriber-level access or above inject arbitrary JavaScript through a submitted listing image title (post_images / file_info[2]). The injected script is persisted in the database and executes in the browser of any user who later views the affected listing or map view, scoring 6.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) with a scope change because the script runs in the context of the vulnerable site. Exploitation is gated by the need for a valid low-privilege account (the target site must allow registration or the attacker must already hold credentials) and by a victim subsequently loading the tainted page; no public exploit code has been identified at time of analysis.
Stored cross-site scripting in GeoDirectory WordPress plugin versions through 2.8.190 allows authenticated attackers with subscriber-level access or higher to inject arbitrary scripts through the 'post_title' parameter, which then execute when a victim views the affected listing or page. Exploitation requires a low-privilege account and site settings that permit listing or post submission, and it is not unauthenticated; no public exploit was identified at time of analysis. The CVSS 6.4 score reflects scoped script execution with low confidentiality and integrity impact.
Stored cross-site scripting in the PO/MO Editor WordPress plugin, affecting all versions up to and including 1.4.2, allows an authenticated attacker with subscriber-level access or higher to inject arbitrary script through the 'podata' parameter, which the plugin persists and later serves as a replacement .po/.mo translation file via its load_textdomain_mofile filter. Because the injected translation is rendered for any visitor loading an affected page, a low-privilege account on a site with open registration enabled is sufficient to seed persistent script execution in other users' browsers; the CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N, score 6.4) reflects network reachability, no user interaction beyond page view, scope change, and limited confidentiality and integrity impact with no availability effect. Exploitation requires the plugin to be installed and active plus a valid low-privilege account, and no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis.
Stored cross-site scripting in the Booking Package WordPress plugin (versions up to and including 1.7.29) allows authenticated users with contributor-level access or higher to inject persistent JavaScript via the 'id' parameter, which executes when other users view the injected page. The flaw results from insufficient input sanitization and output escaping, and no public exploit has been identified at time of analysis. Exploitation requires an authenticated contributor account, and the impact is constrained to higher-privileged users who access the malicious content, making this a moderate-severity issue.
Stored cross-site scripting in the PeproDev Branches Map (Mapify) WordPress plugin affects every release up to and including 3.0.1, allowing an authenticated attacker holding Contributor-level or higher privileges to save script payloads into plugin-handled page or map content that are later rendered without escaping. The injected script then executes in the browser of any user - including administrators and ordinary visitors - who views the compromised page, yielding a CVSS 3.1 base score of 6.4 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) and a scope change that pushes impact beyond the vulnerable component into the wider WordPress session context. Exploitation requires a valid low-privileged authoring account plus a separate victim viewing the poisoned page; on sites with open registration or loosely granted contributor roles that prerequisite is easy to satisfy, and no public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV).
Stored cross-site scripting in the Social Share Buttons & Analytics plugin - GetSocial.io for WordPress (all versions up to and including 4.5) lets an authenticated attacker with at least subscriber-level access save arbitrary JavaScript through the 'response' parameter into the gs-alert-msg, gs-alert-utm and gs-alert-cta options, which then executes in an administrator's browser when the GetSocial settings page is opened. Exploitation is constrained: the payload is not immediate and only fires on that specific wp-admin page, and the attacker must already hold a low-privileged account on the target site (for example through open registration). There is no public exploit code identified at time of analysis and the CVE is not listed in CISA KEV; the assessment is that this is a genuinely moderate, not high-priority, issue.
Stored cross-site scripting in the Directorist WordPress plugin (AI-Powered Business Directory, Listings & Classified Ads) affects all versions up to and including 8.10.2.1, letting an attacker with a subscriber-level account inject arbitrary JavaScript through the 'phone' listing field that then executes in the browser of any user viewing the affected listing page. The weakness is reachable because the plugin grants the edit_at_biz_dirs and publish_at_biz_dirs capabilities to the subscriber role by default, so a subscriber can submit and publish a listing with no administrator moderation; the primary real-world prerequisite is therefore a site that allows open or self-service user registration. Rated CVSS 6.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) and tracked as CVE-2026-100185 by Wordfence, this is a moderate-severity issue that sits below top-priority status, and at the time of analysis there is no public exploit identified and no CISA KEV confirmation of active exploitation, though the low privilege bar makes it more practical than its modest impact metrics suggest.
FV Player 8 through 8.1.7 permits stored cross-site scripting via the synopsis shortcode attribute, allowing authenticated users with contributor-level access or higher to inject scripts that execute when any visitor views the affected page. Sites that enable the non-default 'Parse Vimeo and YouTube links' (parse_comments) setting are also exposed to unauthenticated injection through comment text because the plugin processes shortcodes in comments. The vendor fixed this in 8.1.8; no public exploit identified at time of analysis and no CISA KEV active exploitation confirmed.
Successful TOTP second-factor codes in FileRise prior to 3.23.0 can be replayed from a separate pending-login session, allowing an attacker who already holds the target account's valid username and password to complete authentication and reach that account with high confidentiality and integrity impact. The flaw exists because the application (CWE-287, Improper Authentication) validates a submitted code against the accepted time window but never records that the same account and time step was already consumed, so a captured still-valid code keeps working until the window expires. Exploitation is a narrow, targeted race - it requires possession of the primary credential plus capture of a live code during a genuine victim login (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N, base 6.4) - and no public exploit code is identified at time of analysis; a vendor patch in version 3.23.0 is available.
Stored cross-site scripting in the WordPress plugin Countdown Timer - Widget Countdown through version 3.0.1 allows an authenticated attacker with contributor-level access or higher to inject arbitrary JavaScript into pages by supplying a malicious 'redirect_url' shortcode attribute. Because the payload is persisted, the script executes in the browser of any user - including administrators - who later views the injected page, yielding limited confidentiality and integrity impact within the affected site's origin (CVSS 6.4, AV:N/AC:L/PR:L/UI:N/S:C). There is no public exploit identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV); exploitation is gated by the requirement for a contributor-or-higher account on a site running the plugin.
Missing authorization in the we-mp-rss export download endpoint (/api/v1/wx/tools/export/download) through version 1.5.3 lets unauthenticated remote attackers retrieve export archives stored under data/docs and, by setting delete_after_download=true, delete them - the endpoint's authentication dependency is commented out in apis/tools.py. Exploitation is not unconditional: a target archive must already exist, and the attacker must supply a valid mp_id and correctly guess the timestamp-based export filename, which is the limiting factor reflected in the assessed AT:P rating. No public exploit code identified at time of analysis; the result is unauthorized disclosure of low-sensitivity export data plus possible data loss, making this a moderate, context-dependent risk rather than a top-priority emergency.
A time-of-check/time-of-use race in the DPDK vhost library's handling of virtio indirect descriptor tables allows an attacker who already controls a guest VM attached to a DPDK vhost-user backend to crash or disrupt the host vhost process by mutating the descriptor table length between the host's two reads from guest memory, or by supplying an out-of-range next index against a small host-side copy in the vDPA relay path. Exploitation requires local/guest-level low privilege (PR:L) and is heavily timing-dependent (AC:H), and the impact is confined to availability - the out-of-bounds bytes are consumed internally as descriptor fields for GPA translation and are never returned to the guest as payload, so no confidentiality or integrity loss is assessed. This is a moderate, defense-in-depth-class residual of the CVE-2018-1059 fix rather than an urgent priority, and no public exploit code was identified at time of analysis.
Denial of service in the HPE NonStop TMF Auditread2 audit-trail utility arises from a stack-based buffer overflow (CWE-121) that can be triggered when the utility processes specially crafted input, crashing the process and disrupting availability of the TMF audit-read function. Exploitation is not remote: the assessed vector (AV:L/AC:H/PR:L/UI:N) requires local, authenticated access to the NonStop host plus the ability to execute or feed crafted data to Auditread2, and the high attack complexity means reliable triggering is not trivial. Vendor scoring is 6.4, while our independent assessment rates the impact as availability-only (A:H), so realistic risk is confined to insiders or post-compromise actors on specialized NonStop deployments; no public exploit code has been identified and there is no confirmed active exploitation (CISA KEV) at time of analysis.
Server-side request forgery in ONLYOFFICE DocumentServer before 10.0.0 lets unauthenticated remote attackers coerce the server into fetching arbitrary internal, loopback, and cloud-metadata URLs through the /downloadfile/:docid endpoint and proxy the responses back to the requester. The flaw is reachable in the default configuration because JWT verification is disabled out of the box and a crafted request body setting the isInJwtToken flag causes the fetch to be processed as a DIRECT request, skipping the private-address request-filtering-agent; instances that have explicitly enabled JWT verification are not exploitable through this path. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, but the highest-value impact is on cloud-hosted deployments where reachable metadata services can expose IAM credentials, making this a genuine but moderate-priority issue (CVSS 6.3) rather than a critical emergency.
TLS 1.2 session resumption in the Erlang/OTP ssl application can let a client holding a certificate trusted by one SNI virtual host authenticate to a second SNI virtual host served from the same listen socket, because the per-listener pre-TLS 1.3 session cache is not bound to the SNI name or the trust policy that established it. The flaw is exploitable only under a specific configuration: pre-TLS 1.3 negotiation, multiple SNI names sharing one server certificate (wildcard or multi-SAN), an SNI option set that switches to verify_peer without explicitly setting reuse_sessions, and an attacker who already possesses a client certificate trusted by at least one of the virtual hosts; TLS 1.3 is unaffected. CISA KEV does not list this issue and no public exploit code was identified at time of analysis, though EPSS-style urgency is low given a published vendor patch. The published CVSS 4.0 score is 6.3 (PR:N), while independent assessment rates it around CVSS 3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N - a genuine but conditional trust-confusion/authentication-bypass issue rather than a mass-exploitation priority.
3proxy versions 0.9.7 through 1.0.1 can disclose uninitialized stack memory to remote, unauthenticated attackers who can reach the SOCKS listener when the non-default external-NAT option (-Ne) is configured. A crafted client probe that deliberately fails the SOCKS version check causes the proxy to emit a reply built from an uninitialized sin structure, leaking a few high bytes of a userspace pointer and thereby weakening ASLR; because the leak is partial (not a full memory read) and only reachable under the -Ne deployment setting, overall risk is moderate. No public exploit code has been identified at time of analysis and there is no confirmation of active exploitation (CISA KEV); the fix is available upstream as commit 206c923 but no tagged release containing it has been independently confirmed.
Denial of service in the qs npm query-string library (6.7.0 through 6.16.0) lets an unauthenticated remote attacker force a synchronous TypeError in any application that re-serializes attacker-influenced data with qs.stringify and the non-default option arrayFormat: 'comma'. The crash is triggered when an array element cannot be string-coerced, such as an object with an own non-callable toString ({"toString":"x"}) or a null-prototype object; such elements survive parsing when the application uses qs.parse with allowPrototypes or plainObjects enabled (the defaults for Express 4's query parser, Express 5's extended parser, and body-parser's urlencoded({extended:true})), or when a parsed JSON body is re-serialized. Publicly available proof-of-concept code exists in the vendor advisory, and the reported CVSS v4 score is 6.3, although an independent CVSS 3.1 assessment rates it lower (AC:H, availability impact Low) because the non-default comma serialization path must exist in the target application; realistic impact is a framework-caught HTTP 500, with full process termination only where the call runs outside an error boundary. Vendor-released patch: 6.16.1.
A one-byte heap out-of-bounds read in miniupnpc through 2.3.3 lets an attacker on the same local network crash a UPnP client by responding to discovery or SOAP traffic with a crafted XML element name that ends in a namespace-prefix colon. The minixml parser's parseelt function advances past the ':' character without re-checking the end-of-buffer pointer, so a single byte beyond the heap allocation is read, producing a client-side denial of service at worst. No CISA KEV listing exists, but publicly available exploit code exists (a technical write-up detailing the minixml OOB read), while the assessed impact is limited to availability loss (CVSS 3.1 AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L; vendor score 2.3 on the CVSS 4.0 scale).
miniupnpc through 2.3.3 contains a one-byte heap out-of-bounds read in the minixml parser's parseatt() routine: a malicious or spoofed UPnP Internet Gateway Device on the local network can return a crafted device description or SOAP response whose attribute list ends with an '=' character, causing the client to read one byte past the end of its buffer and crash. Publicly available exploit code exists (a detailed write-up is linked alongside the upstream fix), but there is no confirmed active exploitation; the flaw is rated CVSS 2.3 (CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:N, low availability-only impact), so the realistic outcome is a limited denial of service for unauthenticated attackers who already share the victim's adjacent network and can spoof the gateway. No code execution or data disclosure is associated with this issue.
Unauthenticated visitors to WordPress sites running bbPress before 2.6.19 with the BuddyPress integration enabled can read the title, permalink and body of topics and replies posted in public subforums that are nested beneath a private or hidden parent forum. The flaw arises because the hide_sitewide flag applied to BuddyPress activity entries is derived only from a forum's own visibility and ignores the visibility of ancestor forums, so restricted content continues to surface through the sitewide activity stream and the activity REST endpoint. No public exploit code was identified at time of analysis and the issue is not confirmed as actively exploited; exploitation is configuration-dependent (AT:P) and exposure is limited to confidentiality of already-posted forum content, with no integrity or availability impact, so this is a genuine but moderate-priority authorization/disclosure defect rather than a high-urgency threat.
Authorization bypass in the holaOS channel-gateway Telegram connector (holaOS through 2026.822.1) allows an attacker who registers a released Telegram username that appears in an operator's allowFrom list to submit turns to the bound workspace agent, which then runs the operator's configured tools on their machine. The root cause is that the connector authorizes senders by mutable Telegram username rather than by immutable numeric Telegram ID, yielding limited confidentiality and integrity impact (CVSS 4.0 base 6.3; independent assessment maps to CVSS 3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N). Exploitation is opportunistic and targeted rather than reliably repeatable, since it requires an allowlisted username to be relinquished and re-registered by the attacker, and no public exploit was identified at time of analysis.
HTTP header injection in FreeRDP 3.0.0 through 3.31.x allows a remote unauthenticated RDP client to alter HTTP request framing at an upstream proxy when the FreeRDP proxy is deployed with FixedTarget=false and forwards connections through that proxy. The issue stems from a lone line feed (LF) in the routing token target (Cookie: msts=) that is not rejected and gets written into the CONNECT request line and Host header. The impact is limited to integrity of HTTP requests at the upstream proxy; no public exploit identified at time of analysis, and the configuration prerequisites (FixedTarget=false plus an upstream HTTP proxy) constrain exposure.
Rate-limit bypass in Better Auth (better-auth and @better-auth/drizzle-adapter 1.6.17 through 1.7.6, plus @better-auth/kysely-adapter 1.6.17 up to but not including 1.7.0) lets remote unauthenticated attackers defeat throttling on password sign-in, two-factor verification, one-time-code and password-reset endpoints by firing bursts of concurrent requests that all pass the limit check before any counter update lands. It is rated moderate (CVSS 4.0 6.3; independent assessment CVSS 3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N) because success depends on achieving genuine request concurrency inside a narrow check-then-update window, and the realized impact is defeat of throttling that can enable credential or one-time-code guessing rather than direct data or system compromise. No CISA KEV listing and no public exploit identified at time of analysis; the bypass only applies where the deployment uses Better Auth database-backed rate limiting with a PostgreSQL store and has rate limiting enabled on the targeted endpoints.
Unauthenticated attackers can execute workflows belonging to unrelated projects on n8n instances by omitting the server-generated identifier from requests to dynamic-path webhook, form, or MCP routes, which the platform resolves on the path component alone. The flaw affects n8n before 1.123.83, 2.x before 2.41.4, and 2.42.x before 2.42.1, and exploitation requires no credentials or user interaction - only network reachability and an instance that has at least one deployed dynamic-path trigger configured. Impact is bounded to the workflows and stored credentials of the affected projects (assessed CVSS 3.1 6.3, AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N); no public exploit code has been identified at time of analysis, though the omission technique is trivial to attempt and vendor advisories are public.
Missing authentication for the Go pprof debug endpoints in frp (fatedier/frp) versions 0.41.0 through 0.71.1 lets unauthenticated remote attackers reach /debug/pprof/ on an exposed frps dashboard listener or frpc admin listener, because those handlers are registered on the root HTTP mux outside the Basic Authentication middleware that protects the rest of those interfaces. An attacker can therefore retrieve process command lines, goroutine stacks and heap profiles, and can trigger on-demand CPU profiling, resulting in limited information disclosure and a limited availability impact on the affected listener. Exploitation is configuration-dependent: it requires the dashboard (frps) or admin (frpc) HTTP listener to be enabled and network-reachable, and credentials configured for those interfaces do not help since the pprof routes bypass them. No public exploit code or confirmed active exploitation was identified at time of analysis; CVSS 4.0 base score is 6.3 and the independent assessment rates this a medium-severity, defense-in-depth issue rather than a top-tier emergency.
Command injection in Palo Alto Networks PAN-OS allows an authenticated administrator who can reach the management interface to bypass system restrictions and execute arbitrary commands as root on PA-Series and VM-Series firewalls and on Panorama (virtual and M-Series). Because exploitation requires valid administrator credentials plus network reachability to the management plane, real-world risk is materially reduced by following Palo Alto's best practice of restricting management-interface access to trusted internal IP addresses; Cloud NGFW and Prisma Access are explicitly not affected. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and the vendor-assigned CVSS 4.0 base score is 6.1 (Urgency: Amber), making this a moderate rather than top-tier priority.
Arbitrary OS command execution on managed remote endpoints is possible in Palo Alto Networks Cortex XSOAR and Cortex XSIAM deployments that use the OS Query content pack, where an authenticated administrator can exploit command injection in the pack's command-building logic. Affected environments are limited to those with the OS Query content pack installed and operational; exploitation requires high administrative privileges and no user interaction. No public exploit has been identified at time of analysis, and the risk is assessed as legitimate but not top-tier priority given the privileged access prerequisite.
Cross-organization IDOR in Formbricks server actions before 4.9.0 allows an authenticated owner or manager of any organization to delete survey responses, modify segments and quotas, or tamper with pending invitations belonging to other tenants by pairing their own organizationId with victim resource IDs. Exploitation requires a valid account holding owner or manager privileges (PR:L) plus knowledge of target identifiers such as surveyId, segmentId, quotaId, or invitation ID (AT:P), which confines meaningful risk to multi-tenant or shared deployments where mutually untrusted organizations coexist. Formbricks 4.9.0 resolves the flaw by deriving organization and project ownership server-side from the resource rather than trusting client input; no public exploit code or confirmed active exploitation was identified at time of analysis.
Heap-based buffer overflow in FreeRDP versions 2.0.0 through 3.31.x, when built with WITH_LAME=ON and WITH_DSP_FFMPEG=OFF, allows a malicious RDP server to crash the client by sending crafted MP3 audio over the rdpsnd channel, resulting in a client-side denial of service. Exploitation requires the victim to connect to a malicious or compromised RDP server and the specific non-default build configuration; no public exploit code has been identified at time of analysis. The overall risk is moderate and conditional.
Authorization bypass in n8n's agent chat resume endpoint allows an authenticated member of a shared n8n project to read other members' private agent conversations and approve their pending tool calls, causing those tools to execute and write results back into the victim's conversation. The flaw affects n8n releases before 2.41.4 and 2.42.0 and is rooted in an insecure direct object reference (CWE-639): the resume endpoint accepts a run identifier from the request body without verifying that the referenced suspended checkpoint belongs to the caller. Exploitation requires a valid project-member account (PR:L) plus the stateful condition that another user's agent-chat checkpoint is currently suspended and awaiting tool-call approval (AT:P), so this is primarily a multi-tenant or shared-project insider risk; no public exploit code or confirmed active exploitation was identified at time of analysis, and the assessed severity is moderate (CVSS 3.1 base 6.1, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N).