SQL injection in code-projects Barangay Resident Profiling Management System 1.0 allows unauthenticated remote attackers to manipulate database queries via the Search argument in residents.php. The Resident Search Functionality fails to sanitize user-supplied input before constructing SQL statements, enabling read, write, or denial-of-service impact against the underlying database. A public proof-of-concept exploit is available on GitHub, lowering the bar for opportunistic exploitation; however, the product's extremely limited real-world deployment significantly constrains actual attack surface.
Null pointer dereference in llama.cpp's ggml-RPC server (commit bec4772f6) allows remote unauthenticated denial of service against any deployment exposing the RPC port to the network. The flaw resides in rpc_server::graph_compute, where a graph node with id=0 bypasses a conditional null check, enabling a single crafted TCP packet to crash the server process. No standalone exploit code is publicly available at time of analysis, though the upstream fix PR includes a Python test script that reproducibly triggers the crash in under one second.
Improper input validation in llama.cpp's ggml-RPC Server allows remote unauthenticated attackers to send crafted deserialization payloads targeting the `deserialize_tensor` function, affecting the `op` and `op_params` arguments in `ggml/src/ggml-rpc/ggml-rpc.cpp` at commit bec4772f6. The CVSS 4.0 score of 6.9 (AV:N/AC:L/PR:N/UI:N) reflects network-accessible exploitation with partial confidentiality, integrity, and availability impact on the vulnerable system. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, and the originating GitHub issue was closed due to inactivity.
Directory traversal in WebToffee WooCommerce PDF Invoices, Packing Slips, Delivery Notes & Shipping Labels plugin (all versions ≤ 4.9.8) allows subscriber-level authenticated attackers to read arbitrary server files via the get_image_src_in_base64 function. The exfiltration channel is particularly stealthy: base64-encoded file contents are embedded into cached invoice HTML and retrieved through the plugin's own legitimate Print/Download endpoints using only a valid nonce and access key, potentially bypassing WAF rules that inspect request paths. No public exploit or CISA KEV listing is identified at time of analysis; however, the trivially low privilege bar - any registered WooCommerce customer qualifies - combined with high-value targets like wp-config.php credentials makes this an operational priority for any public-facing WooCommerce store.
Unauthenticated remote access to the cookies.txt file in MeTube (versions up to 2026.06.10) exposes yt-dlp session cookies via a direct HTTP request to the predictable path /download/.metube/cookies.txt. Any remote actor who can reach the MeTube instance can retrieve cookies potentially authenticating to YouTube or other streaming platforms, enabling session hijacking on those services. A public exploit has been disclosed; upgrading to version 2026.06.20 resolves the issue.
Authentication bypass in vas3k TaxHacker through version 0.8.2 is possible because the JWT Secret Handler in `lib/config.ts` falls back to a hard-coded value for `BETTER_AUTH_SECRET` when the environment variable is not explicitly set at deployment. Because TaxHacker is open-source on GitHub, the default secret is publicly readable, enabling any remote unauthenticated attacker to forge valid JWT tokens and impersonate arbitrary users - including administrators - against any misconfigured instance. No vendor patch exists; the maintainer had not responded to the disclosure issue at time of analysis, and publicly available exploit code is indicated by the CVSS 4.0 E:P flag.
Server-side request forgery in vas3k TaxHacker up to version 0.8.2 enables authenticated remote attackers to force the application server to initiate arbitrary IMAP TCP connections to attacker-controlled hosts and ports via the Email Sync configuration interface. The `buildImapConfig` function in `lib/email-sync/imap-client.ts` accepted unsanitized `host` and `port` parameters with no allowlist validation, no private-IP blocking, and no port restriction, allowing the TaxHacker server process to be redirected as a proxy into the internal network. No public exploit is identified at time of analysis; the upstream fix (PR #170) introduces a dedicated validation module but awaits merge acceptance and has not been released in a tagged version.
HTTP request smuggling in the Perl CPAN module Reverse::Proxy (versions before 0.04) allows unauthenticated remote attackers to inject arbitrary HTTP requests to upstream servers by embedding CRLF sequences in percent-encoded URL paths. The PSGI specification requires servers to percent-decode PATH_INFO before handing it to the application, meaning %0d%0a has already become a literal carriage return and line feed by the time the proxy appends it to the upstream request line - terminating that line early and promoting everything that follows to a second, attacker-controlled request. The injected request is attributed to the proxy by the upstream and can reach internal paths the proxy's own routing never exposes; on pooled keep-alive connections it may be delivered in the context of another client's session. No public exploit code and no CISA KEV listing exist at time of analysis.
Cross-site scripting in justhtml 0.9.0-1.21.0 allows an attacker who can control the text content of HTML code or pre elements to escape the Markdown inline code span produced by to_markdown(), causing sanitized content to be emitted unescaped and re-parsed as live HTML by a downstream Markdown renderer. The to_markdown() function is explicitly documented as a security boundary, making this a trust-model violation. No public exploit code has been identified and CISA KEV status is not confirmed, but the root cause is a fundamental gap in the inline code-span helper that bypasses the library's own stated sanitization guarantees.
Cross-site scripting in justhtml before 3.11.0 allows remote unauthenticated attackers to execute arbitrary JavaScript in victims' browsers via SVG or MathML elements injected through selectedcontent projections. The default sanitizer fails to remove event handlers that are cloned and reinserted during the selectedcontent projection process, bypassing the library's intended sanitization guarantees. No public exploit code has been identified at the time of analysis, and a vendor patch (3.11.0) is available; EPSS data was not provided but the CVSS 4.0 score of 5.1 reflects the user-interaction requirement limiting opportunistic exploitation.
Mutation XSS in justhtml (versions ≤1.11.0) allows injection of arbitrary HTML into serialized output when applications use a custom sanitization policy that retains raw-text elements such as <style> or <script>. Attacker-controlled text node content containing a closing tag sequence causes the serializer to break out of the raw-text context, inserting attacker-supplied markup into the final HTML string rendered by a victim's browser. No public exploit has been identified at time of analysis, but a vendor-released patch exists in version 1.12.0.
Mutation XSS (mXSS) in justhtml 1.13.0 and earlier enables markup injection bypass against applications using non-default custom SanitizationPolicy configurations that preserve foreign namespaces. Specially crafted input sanitizes to apparently clean markup that is subsequently reinterpreted as executable script when re-parsed by a browser - a classic parser-differential attack. No public exploit identified at time of analysis and this CVE is not in CISA KEV; however, the no-special-authentication-required network attack vector and the availability of a confirmed patch commit make prompt upgrading the correct response for any application using affected custom policies.
Cross-site scripting in justhtml versions before 1.13.0 allows attackers who control `<pre>` element content to break out of fixed-length Markdown code fences and inject raw HTML into the serialized output. When an application passes attacker-supplied HTML through `JustHTML(..., sanitize=True).to_markdown()` and a downstream CommonMark or GFM renderer processes the result with raw-HTML enabled, the injected script executes in the victim's browser. A proof-of-concept with full reproduction steps is publicly available in the GHSA advisory; no public exploit identified at time of analysis beyond that PoC.
Sanitization bypass in justhtml (Python HTML sanitization library) before version 1.17.0 enables cross-site scripting in applications using custom policies that preserve SVG or MathML namespaces, custom policies that preserve <style> blocks, or programmatic DOM construction prior to serialization. Crafted HTML input containing mutation-XSS parser-differential payloads, HTML integration points such as SVG <foreignObject> or MathML <annotation-xml encoding="text/html">, or resource-loading CSS constructs can survive sanitization and activate as executable markup after browser reparse. No public exploit code has been identified and the CISA KEV list does not list this CVE; notably, the default JustHTML(..., sanitize=True) configuration is not affected by most of the reported issues.
Missing capability check in WooCommerce Bookings WordPress plugin before 3.9.0 allows any authenticated user with Subscriber-level access or above to create draft bookable products via a vulnerable AJAX endpoint. The nonce check that would normally prevent unauthorized requests can be defeated by simply omitting the nonce token from the request - a particularly low-friction bypass. No public exploit has been identified at time of analysis, and the EPSS score of 0.19% (9th percentile) reflects low observed exploitation interest.
Broken access control in Brave Popup Builder WordPress plugin (versions through 0.8.5) allows any authenticated low-privilege user - including Subscriber-level or WooCommerce Customer accounts - to read restricted popup content by supplying an arbitrary post ID in the URL. The flaw is classified as CWE-639 (Authorization Bypass Through User-Controlled Key), an IDOR pattern where the server fails to validate whether the requesting user has rights to the resource identified by a user-supplied key. No active exploitation has been identified and EPSS sits at the 8th percentile, though the low barrier to exploitation (any authenticated user) means the attack surface on multi-tenant or membership-based WordPress sites is broader than the CVSS score alone suggests.