Monthly
An authentication bypass in Parse Server affects 8.x releases before 8.6.102 and 9.0.0 through 9.10.5-alpha.2 when an app is configured with a custom authentication adapter written as a subclass of the exported AuthAdapter class: Parse Server never invokes the subclass's validateSetUp, validateLogin, and validateUpdate methods and instead falls back to an inherited base-class default that accepts any authData. For any provider served by such an adapter, unauthenticated remote attackers can supply arbitrary authData to sign up, link an identity, log in as an existing user, or skip a custom adapter that implements an additional authentication factor, potentially gaining full account access and integrity over affected data. Apps using built-in adapters or custom adapters defined as plain objects are not affected, and no public exploit code was identified at time of analysis; the priority label from the reporting feed is act_now, reflecting that the impact is severe for the narrower population that matches the configuration prerequisite.
Authentication bypass in the asVereinbase WordPress plugin before 1.1.8 allows unauthenticated remote attackers to log in as any user, including an administrator, because the plugin accepts an empty stored password or second-factor value as a match. Affected are WordPress sites running the plugin at versions below 1.1.8; the CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N with high confidentiality, integrity and availability impact, and no special configuration or user interaction is required. A public PoC reference exists but is not verified as working exploit code, and the EPSS score is low at 0.19% (8th percentile) even though the vuln.today decision label is act_now, so the severity and priority signals are split and should be read together.
OpenID Connect login in Goobi viewer 25.01 through 26.04 validates the JWT audience outside the cryptographic verifier, so an ID token minted for a different relying party on the same identity provider can be replayed to the viewer's authentication endpoint and log the attacker in as that token's subject. Only deployments that have opted into OpenID authentication and share an IdP/issuer with at least one other relying party are exposed; array-valued aud claims fail closed and single-RP setups are described by the vendor as not practically exploitable, and the viewer's per-login nonce/state binding narrows the window further. There is no KEV entry and no public exploit identified at time of analysis, but a fixed release (26.05) and the upstream commit are both public. EPSS was not supplied in the input.
Goobi Viewer deployments that leave webapi.authorization.token unset accept an empty ?token= value on every @AuthorizationBinding-protected REST endpoint, allowing an unauthenticated caller to invoke protected API methods. The official install guide generates a UUID token, so only installations that skipped that bootstrap step - typically test, staging, CI, or container images - are exposed; on those, an attacker can delete Solr records, read operational statistics and cache data, and, where the client-applications feature is used, read client secrets and grant a client access to restricted content. The issue is fixed in version 26.05, and no public exploit was identified at the time of analysis.
Unauthenticated remote agent invocation in PraisonAI LinearBot 4.6.56 through 4.6.58: because LINEAR_WEBHOOK_SECRET is treated as optional and defaults to an empty string, the aiohttp webhook listener bound to 0.0.0.0 skips Linear-Signature HMAC verification entirely, so any network caller who can reach the endpoint can POST a forged 'Linear-Event: AgentSession' request that is parsed, backgrounded, and dispatched into BotSessionManager.chat(), causing the bot to run the configured agent and post comments back to Linear under the bot token. Exploitation requires the operator to have started LinearBot with a Linear token but without a webhook secret, and the listener to be reachable; deployments that do set the secret reject missing and invalid signatures with 401 before dispatch. A public proof-of-vulnerability harness exists that exercises the handler offline and monkey-patches the outbound comment path; it is not verified as working exploit code against deployed instances, and there is no confirmed active exploitation (no KEV entry).
PraisonAI versions 4.5.112 through 4.6.58 expose the Recipe HTTP API without authentication when an operator starts the deprecated Typer command `praisonai recipe serve` on a non-localhost interface without explicitly selecting API-key auth, allowing unauthenticated network callers to enumerate and execute recipes and, when `--admin` is enabled, invoke `/admin/reload`. The issue is an authentication bypass at the installed Typer callsite (CWE-287, with CWE-306 and CWE-862 also applicable); the hardened legacy feature handler rejects non-localhost binding without auth, and `create_auth_middleware()` fails closed with 503/401 when auth is selected but misconfigured. The CVSS 3.1 base score is 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N), and PraisonAI 4.6.59 contains the vendor fix; no CISA KEV entry or confirmed working remote exploit code is present in the supplied intelligence, and the advisory's public local-only proof-of-value harness exercises the bypass in-process without binding a socket, so it is not verified as working remote exploit code. Given the this-week decision label, prioritize upgrading internet-reachable or Docker-deployed instances.
Improper authentication in ASUS router firmware lets an unauthenticated attacker on an adjacent network-such as an associated Wi-Fi client or a device on the same LAN segment-send an HTTP request, forge an access ticket, and perform administrator operations. The affected router models and firmware versions are not specified in the available data, which uses a wildcard CPE for ASUS routers, and no public exploit has been identified at time of analysis. The issue is rated 8.7 and is prioritized this week.
Improper authentication in Microsoft Entra Application Proxy (formerly AAD App Proxy) allows an unauthenticated, remote attacker to elevate privileges across a trust boundary, with the supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N) scoring 10.0 - no privileges, no user interaction and low complexity, with high confidentiality and integrity impact and a scope change. Exposure is deployment-specific: the target organization must actually run Application Proxy to publish internal applications for remote access, and the proxy endpoint must be reachable by the attacker; organizations not using the service are not exposed to this flaw. Microsoft is the reporting party and a vendor patch is available per the MSRC update guide, and the vuln.today decision label is act_now; no public exploit code or confirmed active exploitation was identified in the supplied data, although the trigger conditions themselves are not described in the available sources.
Token forgery in the Authlib Python library before 1.9.1 lets a remote, unauthenticated attacker mint HS256, HS384 or HS512 tokens carrying arbitrary claims that Authlib accepts as genuinely signed, whenever the deploying application's HMAC verification key resolves to an empty string or empty bytes (for example an unset environment variable defaulted to '', a config column defaulting to '', or a key-resolver returning '' on a lookup miss). The exposure is strongly gated by that deployment precondition: applications that always supply a non-empty secret are not exploitable, and asymmetric RS/ES verification paths are unaffected, which is why the vector carries AC:H rather than a universally applicable rating. No public exploit code has been identified at time of analysis (the advisory supplies a prose reproduction description rather than weaponized code), CISA KEV does not list this issue, and the vendor has released 1.9.1 as the fix.
Unauthenticated OAuth state values can be redeemed as Magic Link tokens in Better Auth 1.4.0-beta.18 through 1.7.6, letting an attacker who knows a victim's email address obtain a full session for that account without mailbox access or completing the provider callback. The flaw only applies to deployments that enable the Magic Link plugin with plain token storage (or hashed tokens plus globally hashed verification identifiers), enable a built-in social or Generic OAuth provider, and use database-backed OAuth state - the default when a database or secondary storage is configured. Successful abuse yields an existing user's session with all its permissions, or, when Magic Link sign-up is enabled, a new account incorrectly flagged as email verified; no public exploit code has been identified at time of analysis, but the vendor advisory and a public fix commit fully document the technique.
An authentication bypass in Parse Server affects 8.x releases before 8.6.102 and 9.0.0 through 9.10.5-alpha.2 when an app is configured with a custom authentication adapter written as a subclass of the exported AuthAdapter class: Parse Server never invokes the subclass's validateSetUp, validateLogin, and validateUpdate methods and instead falls back to an inherited base-class default that accepts any authData. For any provider served by such an adapter, unauthenticated remote attackers can supply arbitrary authData to sign up, link an identity, log in as an existing user, or skip a custom adapter that implements an additional authentication factor, potentially gaining full account access and integrity over affected data. Apps using built-in adapters or custom adapters defined as plain objects are not affected, and no public exploit code was identified at time of analysis; the priority label from the reporting feed is act_now, reflecting that the impact is severe for the narrower population that matches the configuration prerequisite.
Authentication bypass in the asVereinbase WordPress plugin before 1.1.8 allows unauthenticated remote attackers to log in as any user, including an administrator, because the plugin accepts an empty stored password or second-factor value as a match. Affected are WordPress sites running the plugin at versions below 1.1.8; the CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N with high confidentiality, integrity and availability impact, and no special configuration or user interaction is required. A public PoC reference exists but is not verified as working exploit code, and the EPSS score is low at 0.19% (8th percentile) even though the vuln.today decision label is act_now, so the severity and priority signals are split and should be read together.
OpenID Connect login in Goobi viewer 25.01 through 26.04 validates the JWT audience outside the cryptographic verifier, so an ID token minted for a different relying party on the same identity provider can be replayed to the viewer's authentication endpoint and log the attacker in as that token's subject. Only deployments that have opted into OpenID authentication and share an IdP/issuer with at least one other relying party are exposed; array-valued aud claims fail closed and single-RP setups are described by the vendor as not practically exploitable, and the viewer's per-login nonce/state binding narrows the window further. There is no KEV entry and no public exploit identified at time of analysis, but a fixed release (26.05) and the upstream commit are both public. EPSS was not supplied in the input.
Goobi Viewer deployments that leave webapi.authorization.token unset accept an empty ?token= value on every @AuthorizationBinding-protected REST endpoint, allowing an unauthenticated caller to invoke protected API methods. The official install guide generates a UUID token, so only installations that skipped that bootstrap step - typically test, staging, CI, or container images - are exposed; on those, an attacker can delete Solr records, read operational statistics and cache data, and, where the client-applications feature is used, read client secrets and grant a client access to restricted content. The issue is fixed in version 26.05, and no public exploit was identified at the time of analysis.
Unauthenticated remote agent invocation in PraisonAI LinearBot 4.6.56 through 4.6.58: because LINEAR_WEBHOOK_SECRET is treated as optional and defaults to an empty string, the aiohttp webhook listener bound to 0.0.0.0 skips Linear-Signature HMAC verification entirely, so any network caller who can reach the endpoint can POST a forged 'Linear-Event: AgentSession' request that is parsed, backgrounded, and dispatched into BotSessionManager.chat(), causing the bot to run the configured agent and post comments back to Linear under the bot token. Exploitation requires the operator to have started LinearBot with a Linear token but without a webhook secret, and the listener to be reachable; deployments that do set the secret reject missing and invalid signatures with 401 before dispatch. A public proof-of-vulnerability harness exists that exercises the handler offline and monkey-patches the outbound comment path; it is not verified as working exploit code against deployed instances, and there is no confirmed active exploitation (no KEV entry).
PraisonAI versions 4.5.112 through 4.6.58 expose the Recipe HTTP API without authentication when an operator starts the deprecated Typer command `praisonai recipe serve` on a non-localhost interface without explicitly selecting API-key auth, allowing unauthenticated network callers to enumerate and execute recipes and, when `--admin` is enabled, invoke `/admin/reload`. The issue is an authentication bypass at the installed Typer callsite (CWE-287, with CWE-306 and CWE-862 also applicable); the hardened legacy feature handler rejects non-localhost binding without auth, and `create_auth_middleware()` fails closed with 503/401 when auth is selected but misconfigured. The CVSS 3.1 base score is 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N), and PraisonAI 4.6.59 contains the vendor fix; no CISA KEV entry or confirmed working remote exploit code is present in the supplied intelligence, and the advisory's public local-only proof-of-value harness exercises the bypass in-process without binding a socket, so it is not verified as working remote exploit code. Given the this-week decision label, prioritize upgrading internet-reachable or Docker-deployed instances.
Improper authentication in ASUS router firmware lets an unauthenticated attacker on an adjacent network-such as an associated Wi-Fi client or a device on the same LAN segment-send an HTTP request, forge an access ticket, and perform administrator operations. The affected router models and firmware versions are not specified in the available data, which uses a wildcard CPE for ASUS routers, and no public exploit has been identified at time of analysis. The issue is rated 8.7 and is prioritized this week.
Improper authentication in Microsoft Entra Application Proxy (formerly AAD App Proxy) allows an unauthenticated, remote attacker to elevate privileges across a trust boundary, with the supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N) scoring 10.0 - no privileges, no user interaction and low complexity, with high confidentiality and integrity impact and a scope change. Exposure is deployment-specific: the target organization must actually run Application Proxy to publish internal applications for remote access, and the proxy endpoint must be reachable by the attacker; organizations not using the service are not exposed to this flaw. Microsoft is the reporting party and a vendor patch is available per the MSRC update guide, and the vuln.today decision label is act_now; no public exploit code or confirmed active exploitation was identified in the supplied data, although the trigger conditions themselves are not described in the available sources.
Token forgery in the Authlib Python library before 1.9.1 lets a remote, unauthenticated attacker mint HS256, HS384 or HS512 tokens carrying arbitrary claims that Authlib accepts as genuinely signed, whenever the deploying application's HMAC verification key resolves to an empty string or empty bytes (for example an unset environment variable defaulted to '', a config column defaulting to '', or a key-resolver returning '' on a lookup miss). The exposure is strongly gated by that deployment precondition: applications that always supply a non-empty secret are not exploitable, and asymmetric RS/ES verification paths are unaffected, which is why the vector carries AC:H rather than a universally applicable rating. No public exploit code has been identified at time of analysis (the advisory supplies a prose reproduction description rather than weaponized code), CISA KEV does not list this issue, and the vendor has released 1.9.1 as the fix.
Unauthenticated OAuth state values can be redeemed as Magic Link tokens in Better Auth 1.4.0-beta.18 through 1.7.6, letting an attacker who knows a victim's email address obtain a full session for that account without mailbox access or completing the provider callback. The flaw only applies to deployments that enable the Magic Link plugin with plain token storage (or hashed tokens plus globally hashed verification identifiers), enable a built-in social or Generic OAuth provider, and use database-backed OAuth state - the default when a database or secondary storage is configured. Successful abuse yields an existing user's session with all its permissions, or, when Magic Link sign-up is enabled, a new account incorrectly flagged as email verified; no public exploit code has been identified at time of analysis, but the vendor advisory and a public fix commit fully document the technique.