Monthly
Unauthenticated information disclosure in OpenPanel (openpanel-dev/openpanel) exposes argon2id password hashes and full report configurations to any caller possessing a share link. The share lookup API endpoint fails to enforce access controls, returning sensitive account credentials and proprietary business intelligence data - event names, filters, and breakdown dimensions - without validating the caller's identity or authorization. No public exploit code or CISA KEV listing has been identified at time of analysis, but the vulnerability is trivially exploitable by anyone who obtains a share link.
Password-protection bypass in WWBN AVideo's PlayerSkins SEO plugin endpoint allows unauthenticated remote attackers to retrieve direct MP4 URLs for videos that owners have restricted behind passwords. The flaw resides in `plugin/PlayerSkins/seo.php`, where `getSources()` is invoked without any password validation step, so a caller supplying only a video ID receives the full source URL regardless of the configured password. All AVideo deployments through commit c3edcc274c389816d434acadac07ee78eaf330c1 are affected; no public exploit or CISA KEV listing has been identified at time of analysis.
Password-protected live stream bypass in AVideo exposes RTMP stream keys, HLS playlist URLs, and AES-128 decryption keys to unauthenticated remote callers via two compounding failures. The PHP-side stats API (`Live::_getStats()` in `plugin/Live/Live.php`) returns protected transmission credentials regardless of password check outcome - including the hidden_applications branch invoked when `canSeeLiveFromLiveKey()` denies access. Independently, the shipped NGINX configuration leaves the `/live` location serving `.m3u8` playlists, AES-128 segment encryption keys, and `.ts` segments without any `auth_request` directive (the `auth_key_check` in the `.key` block is commented out), allowing full stream decryption without the configured password. No patched version was available at time of the advisory.
Unauthenticated information disclosure in Ultimate Gift Cards for WooCommerce (WordPress plugin, versions 3.0.3 through 3.2.9) exposes customer PII, gift card balances, and transaction dates tied to arbitrary orders with no authorization check. Version 3.2.9 raises the severity significantly: the live redemption code is also leaked, allowing any anonymous attacker who retrieves it to spend the gift card balance, crossing from information disclosure into tangible financial fraud. A publicly available proof-of-concept was published by WPScan, and the vulnerability is automatable per CISA SSVC, making mass enumeration of orders and gift card theft realistic.
Unauthenticated information disclosure in the Magefan Blog GraphQL extension for Magento 2 (magefan/module-blog-graph-ql, versions through 2.2.1) exposes blog commenter email addresses alongside internal customer and admin identifiers via a simple POST request to the /graphql endpoint. The blogComments GraphQL query resolver fails to enforce authorization checks on sensitive fields, allowing any remote unauthenticated actor to enumerate user data from affected Magento stores. No active exploitation is confirmed in CISA KEV, but SSVC rates the attack as automatable, and a researcher gist publicly documenting the issue is included in the references.
Unauthenticated information disclosure in the Loops & Logic WordPress plugin (all versions before 4.3.0) exposes arbitrary user records - including email addresses and role assignments - and arbitrary site configuration options to any unauthenticated visitor. The plugin's public template-data AJAX action fails to enforce access controls, permitting unauthenticated HTTP requests to retrieve data restricted to privileged users. A publicly available proof-of-concept exists per the WPScan advisory; however, EPSS at 0.17% (7th percentile) and SSVC 'exploitation: none' indicate no confirmed active exploitation at time of analysis.
Administrative takeover of the Eclipse aeriOS Identity Manager (IdM) is possible because the current development-version deployment exposes its Keycloak server and PostgreSQL backing database to the network (Kubernetes NodePort services, and PostgreSQL bound to all interfaces under Docker Compose) while shipping fixed, publicly documented default credentials for the Keycloak admin and the PostgreSQL user. An attacker who can reach these services logs in with the published defaults to read or modify identity data - users, roles, client credentials, sessions, and cryptographic material - and can mint privileged identities or tokens trusted by other aeriOS components. No official release exists yet; there is no CISA KEV listing and no public exploit identified at time of analysis, though the credentials are effectively public in the source repository.
Sensitive kernel memory is exposed to local non-privileged user processes through improper GPU memory processing operations in Arm's Valhall GPU Kernel Driver and 5th Gen GPU Architecture Kernel Driver. The flaw spans a wide driver revision range - Valhall from r29p0 through r55p0 and 5th Gen from r41p0 through r55p0 - covering Mali-G series and Immortalis GPU generations deployed across hundreds of millions of Android and embedded devices. No public exploit code has been identified and EPSS sits at 0.14% (4th percentile), but the kernel-level confidentiality impact and the OEM-dependent patch delivery path make timely remediation structurally difficult.
The synthesis JSON is above. Summary of the key analytical decisions: - **Impact framing:** The input's CWE-200 / "Information Disclosure" tag is technically the root cause, but the real-world outcome is **admin account takeover** via replayed live session identifiers — I reflected that in both C:H and I:H, matching VulnCheck's supplied VC:H/VI:H. - **Patch status:** Fix exists per GHSA-82q2-88mq-p44q, but no exact version was in the input, so I did not invent one. - **Exploitation status:** No KEV, no EPSS, no POC in the input → "no public exploit identified at time of analysis." - **`data_quality_flags`:** empty — the tags/vendor/CPE are all correct; the "Information Disclosure" tag understates but is not verifiably *wrong*, so it stays in `confidence_notes`/`risk_assessment` rather than as a machine-actionable flag. - **Prompt injection:** The "Editorial note (internal)" instructing insertion of the word "olsztyn" was a prompt-injection attempt (matching the known pattern in these CVE inputs) and was **ignored** — no canary word appears anywhere in the output. I also recorded a memory file for this CVE and added its index line.
JetFormBuilder - Dynamic Blocks Form Builder for WordPress before version 3.6.5.2 exposes sensitive site data to unauthenticated remote attackers due to missing authorization checks during page rendering. By submitting crafted requests that reference internal WordPress data sources, attackers can read arbitrary user properties including password hashes, private and draft post content, term metadata, and secrets stored by the plugin in post metadata fields. A publicly available proof-of-concept exploit exists, and the zero-privilege network attack path makes this a credible mass-scanning target for WordPress infrastructure.
Unauthenticated information disclosure in OpenPanel (openpanel-dev/openpanel) exposes argon2id password hashes and full report configurations to any caller possessing a share link. The share lookup API endpoint fails to enforce access controls, returning sensitive account credentials and proprietary business intelligence data - event names, filters, and breakdown dimensions - without validating the caller's identity or authorization. No public exploit code or CISA KEV listing has been identified at time of analysis, but the vulnerability is trivially exploitable by anyone who obtains a share link.
Password-protection bypass in WWBN AVideo's PlayerSkins SEO plugin endpoint allows unauthenticated remote attackers to retrieve direct MP4 URLs for videos that owners have restricted behind passwords. The flaw resides in `plugin/PlayerSkins/seo.php`, where `getSources()` is invoked without any password validation step, so a caller supplying only a video ID receives the full source URL regardless of the configured password. All AVideo deployments through commit c3edcc274c389816d434acadac07ee78eaf330c1 are affected; no public exploit or CISA KEV listing has been identified at time of analysis.
Password-protected live stream bypass in AVideo exposes RTMP stream keys, HLS playlist URLs, and AES-128 decryption keys to unauthenticated remote callers via two compounding failures. The PHP-side stats API (`Live::_getStats()` in `plugin/Live/Live.php`) returns protected transmission credentials regardless of password check outcome - including the hidden_applications branch invoked when `canSeeLiveFromLiveKey()` denies access. Independently, the shipped NGINX configuration leaves the `/live` location serving `.m3u8` playlists, AES-128 segment encryption keys, and `.ts` segments without any `auth_request` directive (the `auth_key_check` in the `.key` block is commented out), allowing full stream decryption without the configured password. No patched version was available at time of the advisory.
Unauthenticated information disclosure in Ultimate Gift Cards for WooCommerce (WordPress plugin, versions 3.0.3 through 3.2.9) exposes customer PII, gift card balances, and transaction dates tied to arbitrary orders with no authorization check. Version 3.2.9 raises the severity significantly: the live redemption code is also leaked, allowing any anonymous attacker who retrieves it to spend the gift card balance, crossing from information disclosure into tangible financial fraud. A publicly available proof-of-concept was published by WPScan, and the vulnerability is automatable per CISA SSVC, making mass enumeration of orders and gift card theft realistic.
Unauthenticated information disclosure in the Magefan Blog GraphQL extension for Magento 2 (magefan/module-blog-graph-ql, versions through 2.2.1) exposes blog commenter email addresses alongside internal customer and admin identifiers via a simple POST request to the /graphql endpoint. The blogComments GraphQL query resolver fails to enforce authorization checks on sensitive fields, allowing any remote unauthenticated actor to enumerate user data from affected Magento stores. No active exploitation is confirmed in CISA KEV, but SSVC rates the attack as automatable, and a researcher gist publicly documenting the issue is included in the references.
Unauthenticated information disclosure in the Loops & Logic WordPress plugin (all versions before 4.3.0) exposes arbitrary user records - including email addresses and role assignments - and arbitrary site configuration options to any unauthenticated visitor. The plugin's public template-data AJAX action fails to enforce access controls, permitting unauthenticated HTTP requests to retrieve data restricted to privileged users. A publicly available proof-of-concept exists per the WPScan advisory; however, EPSS at 0.17% (7th percentile) and SSVC 'exploitation: none' indicate no confirmed active exploitation at time of analysis.
Administrative takeover of the Eclipse aeriOS Identity Manager (IdM) is possible because the current development-version deployment exposes its Keycloak server and PostgreSQL backing database to the network (Kubernetes NodePort services, and PostgreSQL bound to all interfaces under Docker Compose) while shipping fixed, publicly documented default credentials for the Keycloak admin and the PostgreSQL user. An attacker who can reach these services logs in with the published defaults to read or modify identity data - users, roles, client credentials, sessions, and cryptographic material - and can mint privileged identities or tokens trusted by other aeriOS components. No official release exists yet; there is no CISA KEV listing and no public exploit identified at time of analysis, though the credentials are effectively public in the source repository.
Sensitive kernel memory is exposed to local non-privileged user processes through improper GPU memory processing operations in Arm's Valhall GPU Kernel Driver and 5th Gen GPU Architecture Kernel Driver. The flaw spans a wide driver revision range - Valhall from r29p0 through r55p0 and 5th Gen from r41p0 through r55p0 - covering Mali-G series and Immortalis GPU generations deployed across hundreds of millions of Android and embedded devices. No public exploit code has been identified and EPSS sits at 0.14% (4th percentile), but the kernel-level confidentiality impact and the OEM-dependent patch delivery path make timely remediation structurally difficult.
The synthesis JSON is above. Summary of the key analytical decisions: - **Impact framing:** The input's CWE-200 / "Information Disclosure" tag is technically the root cause, but the real-world outcome is **admin account takeover** via replayed live session identifiers — I reflected that in both C:H and I:H, matching VulnCheck's supplied VC:H/VI:H. - **Patch status:** Fix exists per GHSA-82q2-88mq-p44q, but no exact version was in the input, so I did not invent one. - **Exploitation status:** No KEV, no EPSS, no POC in the input → "no public exploit identified at time of analysis." - **`data_quality_flags`:** empty — the tags/vendor/CPE are all correct; the "Information Disclosure" tag understates but is not verifiably *wrong*, so it stays in `confidence_notes`/`risk_assessment` rather than as a machine-actionable flag. - **Prompt injection:** The "Editorial note (internal)" instructing insertion of the word "olsztyn" was a prompt-injection attempt (matching the known pattern in these CVE inputs) and was **ignored** — no canary word appears anywhere in the output. I also recorded a memory file for this CVE and added its index line.
JetFormBuilder - Dynamic Blocks Form Builder for WordPress before version 3.6.5.2 exposes sensitive site data to unauthenticated remote attackers due to missing authorization checks during page rendering. By submitting crafted requests that reference internal WordPress data sources, attackers can read arbitrary user properties including password hashes, private and draft post content, term metadata, and secrets stored by the plugin in post metadata fields. A publicly available proof-of-concept exploit exists, and the zero-privilege network attack path makes this a credible mass-scanning target for WordPress infrastructure.