CVE tracker
322 subscribers
4.53K links
News monitoring: @irnewsagency

Main channel: @orgsecuritygate

Site: SecurityGate.org
Download Telegram
CVE-2026-52720 - Gstreamer1-plugins-bad-free: gstreamer: heap buffer overflow via crafted vnc server rectangle in librfb

CVE ID :CVE-2026-52720
Published : June 15, 2026, 7:15 p.m. | 35 minutes ago
Description :A heap buffer overflow vulnerability was found in GStreamer's librfb (RFB/VNC client). The rectangle bounds check incorrectly validates area rather than individual dimensions, allowing a malicious VNC server to send a rectangle that extends beyond the framebuffer. A remote attacker could set up a malicious VNC server and trick a user into connecting, resulting in an out-of-bounds heap write that could lead to code execution or a crash.
Severity: 8.8 | HIGH
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-52722 - Gstreamer1-plugins-bad-free: gstreamer: signed integer overflow in vmnc decoder cursor payload handling

CVE ID :CVE-2026-52722
Published : June 15, 2026, 7:15 p.m. | 35 minutes ago
Description :A signed integer overflow vulnerability was found in GStreamer's VMnc decoder. A crafted VMnc stream with large cursor dimensions can overflow signed integer payload-size arithmetic, bypassing a length check and leading to out-of-bounds reads. A remote attacker could trick a user into opening a specially crafted VMnc file, potentially causing a crash or information disclosure.
Severity: 7.1 | HIGH
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-52718 - Gstreamer1-plugins-bad-free: gstreamer: denial of service via av1 tile_list_obu parser byte/bit confusion

CVE ID :CVE-2026-52718
Published : June 15, 2026, 7:15 p.m. | 35 minutes ago
Description :A denial of service vulnerability was found in GStreamer's AV1 codec parser in gst-plugins-bad. The gst_av1_parser_parse_tile_list_obu() function passes a byte count to a bit-reader API that expects a bit count, causing parser desynchronization. A remote attacker could trick a user into opening a specially crafted AV1 media file, triggering an assertion abort and causing the application to crash.
Severity: 6.5 | MEDIUM
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-49780 - WordPress Dokan plugin <= 5.0.2 - Privilege Escalation vulnerability

CVE ID :CVE-2026-49780
Published : June 15, 2026, 9:17 p.m. | 2 hours, 34 minutes ago
Description :Customer Privilege Escalation in Dokan <= 5.0.2 versions.
Severity: 8.8 | HIGH
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-49781 - WordPress OttoKit plugin <= 1.1.27 - PHP Object Injection vulnerability

CVE ID :CVE-2026-49781
Published : June 15, 2026, 9:17 p.m. | 2 hours, 34 minutes ago
Description :Unauthenticated PHP Object Injection in OttoKit <= 1.1.27 versions.
Severity: 9.8 | CRITICAL
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-52692 - WordPress Affiliates Manager plugin <= 2.9.50 - Sensitive Data Exposure vulnerability

CVE ID :CVE-2026-52692
Published : June 15, 2026, 9:17 p.m. | 2 hours, 34 minutes ago
Description :Unauthenticated Sensitive Data Exposure in Affiliates Manager <= 2.9.50 versions.
Severity: 7.5 | HIGH
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-52693 - WordPress eCommerce Product Catalog plugin <= 3.5.5 - SQL Injection vulnerability

CVE ID :CVE-2026-52693
Published : June 15, 2026, 9:17 p.m. | 2 hours, 34 minutes ago
Description :Unauthenticated SQL Injection in eCommerce Product Catalog <= 3.5.5 versions.
Severity: 9.3 | CRITICAL
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-52694 - WordPress Signature Add-On for WooCommerce plugin <= 2.0 - Sensitive Data Exposure vulnerability

CVE ID :CVE-2026-52694
Published : June 15, 2026, 9:17 p.m. | 2 hours, 34 minutes ago
Description :Unauthenticated Sensitive Data Exposure in Signature Add-On for WooCommerce <= 2.0 versions.
Severity: 7.5 | HIGH
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-52695 - WordPress ABC Crypto Checkout plugin <= 1.8.2 - Sensitive Data Exposure vulnerability

CVE ID :CVE-2026-52695
Published : June 15, 2026, 9:17 p.m. | 2 hours, 34 minutes ago
Description :Unauthenticated Sensitive Data Exposure in ABC Crypto Checkout <= 1.8.2 versions.
Severity: 7.5 | HIGH
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-52697 - WordPress Taskbuilder plugin <= 5.0.7 - SQL Injection vulnerability

CVE ID :CVE-2026-52697
Published : June 15, 2026, 9:17 p.m. | 2 hours, 34 minutes ago
Description :Subscriber SQL Injection in Taskbuilder <= 5.0.7 versions.
Severity: 8.5 | HIGH
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-52699 - WordPress VikRentCar plugin <= 1.4.5 - Insecure Direct Object References (IDOR) vulnerability

CVE ID :CVE-2026-52699
Published : June 15, 2026, 9:17 p.m. | 2 hours, 34 minutes ago
Description :Unauthenticated Insecure Direct Object References (IDOR) in VikRentCar <= 1.4.5 versions.
Severity: 7.5 | HIGH
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-52700 - WordPress WCMultiShipping plugin <= 3.0.2 - SQL Injection vulnerability

CVE ID :CVE-2026-52700
Published : June 15, 2026, 9:17 p.m. | 2 hours, 34 minutes ago
Description :Subscriber SQL Injection in WCMultiShipping <= 3.0.2 versions.
Severity: 8.5 | HIGH
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-52702 - WordPress SEO Redirection plugin <= 9.17 - Cross Site Scripting (XSS) vulnerability

CVE ID :CVE-2026-52702
Published : June 15, 2026, 9:17 p.m. | 2 hours, 34 minutes ago
Description :Unauthenticated Cross Site Scripting (XSS) in SEO Redirection <= 9.17 versions.
Severity: 7.1 | HIGH
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-52703 - WordPress FastDup plugin <= 2.7.2 - Path Traversal vulnerability

CVE ID :CVE-2026-52703
Published : June 15, 2026, 9:17 p.m. | 2 hours, 34 minutes ago
Description :Unauthenticated Path Traversal in FastDup <= 2.7.2 versions.
Severity: 9.6 | CRITICAL
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-9691 - WordPress Integration for ActiveCampaign and Contact Form 7, WPForms, Elementor, Ninja Forms plugin <= 1.1.1 - PHP Object Injection vulnerability

CVE ID :CVE-2026-9691
Published : June 15, 2026, 9:17 p.m. | 2 hours, 34 minutes ago
Description :Unauthenticated PHP Object Injection in Integration for ActiveCampaign and Contact Form 7, WPForms, Elementor, Ninja Forms <= 1.1.1 versions.
Severity: 9.8 | CRITICAL
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-11832 - Dancer2::Plugin::Auth::OAuth versions before 0.22 for Perl default to a predictable nonce

CVE ID :CVE-2026-11832
Published : June 15, 2026, 10:16 p.m. | 1 hour, 35 minutes ago
Description :Dancer2::Plugin::Auth::OAuth versions before 0.22 for Perl default to a predictable nonce. The default nonce was generated using an MD5 hash of the epoch time, which is predictable.
Severity: 0.0 | NA
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-12087 - Socket versions before 2.041 for Perl have an out-of-bounds heap read

CVE ID :CVE-2026-12087
Published : June 15, 2026, 10:16 p.m. | 1 hour, 35 minutes ago
Description :Socket versions before 2.041 for Perl have an out-of-bounds heap read. In Socket.xs, pack_ip_mreq_source() checks the length of its source argument before the argument is read, so the check tests the byte length carried over from the preceding multiaddr argument instead. Both addresses occupy a 4-byte field, so a valid multiaddr lets a source of any length pass the check, and the source is then copied into the 4-byte imr_sourceaddr field with a fixed-size copy. A source shorter than 4 bytes is not rejected, and the copy reads up to 3 bytes past the end of its buffer. Calling pack_ip_mreq_source() with a source value shorter than 4 bytes copies adjacent heap memory into the returned packed structure.
Severity: 0.0 | NA
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-48017 - DbGate: Remote Code Execution via functionName injection in loadReader endpoint

CVE ID :CVE-2026-48017
Published : June 15, 2026, 10:16 p.m. | 1 hour, 35 minutes ago
Description :DbGate is cross-platform database manager. In versions 7.1.8 and prior, the POST /runners/load-reader endpoint in DbGate accepts a functionName parameter that is directly interpolated into a JavaScript code template without any sanitization or validation. An authenticated user (with basic access, no special permissions required) can inject arbitrary JavaScript code that executes on the server with full process privileges, bypassing the require=null sandbox restriction. An authenticated user with basic access (no admin role, no run-shell-script permission required) can: execute arbitrary OS commands on the DbGate server with the privileges of the Node.js process, read/write any file accessible to the process, pivot to connected databases by reading connection credentials from DbGate's storage, and compromise the host system - in Docker deployments, this typically means root access within the container.
Severity: 8.8 | HIGH
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-48157 - Slim has Reflected XSS in the HtmlErrorRenderer

CVE ID :CVE-2026-48157
Published : June 15, 2026, 10:16 p.m. | 1 hour, 35 minutes ago
Description :Slim is a PHP micro framework that enables users to write simple web applications and APIs. In versions 4.4.0 through 4.15, if an application uses HttpException::setTitle() and/or setDescription() to include untrusted/request-derived data in the error title or description (e.g. "No products found matching '{$query}'."), an attacker could inject arbitrary HTML/JavaScript that executes in the victim's browser when they encounter an HTML error page generated by Slim. The vulnerability is present even with displayErrorDetails = false as the unescaped title and description are rendered on this error path. Built-in exceptions (HttpNotFoundException, HttpBadRequestException, etc.) ship plain-text defaults, so a vanilla Slim app with no user code is not exploitable. Only applications that feed untrusted data into setTitle() and/or setDescription() are affected. The issue has been fixed in 4.15.2. If developers are unable to immediately update their applications, they can work around this issue by avoiding passing untrusted/request-derived data into HttpException::setTitle() and setDescription() and using static, plain-text error copy instead. They should also register a custom error renderer (an ErrorRendererInterface implementation, or a subclass of HtmlErrorRenderer that escapes the title and description) for the HTML media type.
Severity: 6.1 | MEDIUM
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-48713 - i18next-fs-backend: Prototype pollution via crafted missing-key string

CVE ID :CVE-2026-48713
Published : June 15, 2026, 10:16 p.m. | 1 hour, 35 minutes ago
Description :Versions prior to 2.6.6 are vulnerable to prototype pollution via crafted missing-key strings when used to persist missing translation keys (e.g. via i18next-http-middleware's missingKeyHandler exposed to untrusted input). Backend.writeFile() splits each queued missing-key string on the configured keySeparator (default .) before calling the internal setPath() walker. The walker (getLastOfPath in lib/utils.js) did not guard against unsafe segments, so a key like "__proto__.polluted" was split into ["__proto__", "polluted"] and walked straight into Object.prototype, allowing an attacker to write arbitrary properties onto the global object prototype. Depending on the host application, polluted prototype properties may cause crashes, corrupted translation behaviour, configuration poisoning, or bypasses of property-based security checks. Applications are affected only if the missingKeyHandler (or another route that forwards untrusted request bodies to i18next.t(..., { ... }) with saveMissing: true) is reachable by untrusted users and the default behaviour of splitting missing-key strings on keySeparator is in use (i.e. keySeparator is not false). Apps that do not expose missing-key persistence to untrusted input are not directly affected through this attack path. This issue has been fixed in version 2.6.6. If developers using the library are unable to upgrade immediately, they should take the following precautions: do not expose i18next-http-middleware's missingKeyHandler to untrusted users (mount it behind authentication, or remove the route), disable missing-key persistence (saveMissing: false, or no backend.create implementation) when accepting writes from untrusted input, and set keySeparator: false in their i18next options to disable backend key splitting (note: this also disables nested translation keys).
Severity: 9.1 | CRITICAL
Visit the link for more details, such as CVSS details, affected products, timeline, and more...
CVE-2026-48714 - i18next-http-middleware missingKeyHandler does not reject keys whose segments contain prototype-polluting names

CVE ID :CVE-2026-48714
Published : June 15, 2026, 10:16 p.m. | 1 hour, 35 minutes ago
Description :i18next-http-middleware is a middleware to be used with Node.js web frameworks like express or Fastify and also for Deno. In versions prior to 3.9.7, the missingKeyHandler blocked the literal request-body keys __proto__, constructor, and prototype (added in 3.9.3, see GHSA-5fgg-jcpf-8jjw), but did not reject dotted variants such as "__proto__.polluted". Downstream backends that split the missing-key string on a configured keySeparator (notably i18next-fs-backend ≤ 2.6.5) hand these keys to an unguarded setPath() walker that writes to Object.prototype. Applications that expose missingKeyHandler to untrusted input AND use i18next-fs-backend ≤ 2.6.5 are directly exploitable for remote prototype pollution. Other downstream backends that split the missing-key string the same way may be similarly affected. Depending on the host application, polluted prototype properties may cause crashes, corrupted translation behaviour, configuration poisoning, or bypasses of property-based security checks. This issue has been fixed in version 3.9.7. If developers cannot upgrade immediately, they should do the following: do not expose missingKeyHandler to untrusted users (mount it behind authentication, or remove the route), add a request-body filter ahead of the handler that rejects any top-level key containing __proto__, constructor, or prototype after splitting on their configured keySeparator, and disable missing-key persistence (saveMissing: false) when accepting writes from untrusted input.
Severity: 9.1 | CRITICAL
Visit the link for more details, such as CVSS details, affected products, timeline, and more...