CVE-2026-129945
Keystatic through 0.6.9 contains a login cross-site request forgery vulnerability in the githubOauthCallback handler that allows unauthentic
CVSS
4.3
Média
EPSS
—
KEV
—
Exploit Today
—
0-100
Publicado: 16 de nov. de 2026 · Última mod.: 16 de nov. de 2026 · CWE-352
Ainda não há histórico EPSS suficiente.
Keystatic through 0.6.9 contains a login cross-site request forgery vulnerability in the githubOauthCallback handler that allows unauthenticated remote attackers to sign victims in with the attacker's GitHub account by omitting state validation. Attackers can induce victims to visit the OAuth callback with an attacker-obtained authorization code, causing victim edits in the admin UI to be committed under the attacker's GitHub identity.
- github.comhttps://github.com/Thinkmill/keystatic/blob/b65d4a55501dc3b7bb268dc925d8538a8a9f8e95/packages/keystatic/src/api/generic.ts#L199-L256
- github.comhttps://github.com/Thinkmill/keystatic/blob/b65d4a55501dc3b7bb268dc925d8538a8a9f8e95/packages/keystatic/src/api/generic.ts#L363-L398
- github.comhttps://github.com/Thinkmill/keystatic/issues/1669
- www.vulncheck.comhttps://www.vulncheck.com/advisories/keystatic-through-0.6.9-github-oauth-login-csrf-via-missing-state-validation
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-3860——
———CSRF vulnerability in OpenText Vibe versions <= 4.0.8.7 could expose the token over an insecure connection or make
it accessible to JavaScript, weakening protection against forged requests.7hCVE-2026-113451——
———visualTicket is vulnerable to Cross-Site Request Forgery (CSRF) across multiple endpoints. State-changing operations are exposed via GET requests without any CSRF protection. A remote attacker can persuade an authenticated user (including administrator) into navigating to a prepared URL, causing the victim's browser to issue requests that carry the active session cookie and perform unintended actions.
This issue was partially addressed in version 20260817: settings changes and bulk refunds require POST with a CSRF token, and the session cookie is set with SameSite=Lax, which limits cross-site requests.10hCVE-2026-1230468.8 ALT1.6%
——0The SEOJuice WordPress plugin before 2.12.0 does not correctly restrict a REST API authentication filter, disabling WordPress's REST nonce protection for the whole site and allowing unauthenticated attackers to perform any cookie-authenticated REST action, including creating a new administrator account, by tricking a logged-in administrator into opening a crafted page (CSRF).11hCVE-2026-1272166.5 MÉD8.3%
——3Injection Guard plugin for WordPress before 1.4.0 contains a cross-site request forgery vulnerability that allows unauthenticated attackers to trigger password hash export by tricking a logged-in administrator into loading a crafted link, since the ig_settings admin page in templates/dashboard.php processes GET parameters without nonce verification. Attackers can exploit this to cause the plugin to write WooCommerce customer email hashes and password hashes to an unprotected file at wp-content/plugins/injection-guard/ab-hash.dat, which can then be downloaded without authentication to obtain customer password hashes for offline cracking.3dCVE-2026-631508.1 ALT13.1%
——4Omnispace Agora Project through 26.10.0 contains a cross-site request forgery vulnerability that allows remote attackers to forge privileged actions such as administrator user creation by merging $_GET and $_POST parameters without requiring an anti-CSRF token. Attackers can craft a malicious link or auto-navigating page that issues a plain GET request, exploiting the lack of CSRF protection and SameSite=Lax cookie behavior on top-level navigations to create unauthorized administrator accounts.3dCVE-2026-1280499.0 CRÍ5.4%
——2OpenMage Magento LTS before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 contains a cross-site request forgery vulnerability in the admin and storefront OAuth confirm and confirmSimple actions, which accept GET requests without form-key validation. Attackers holding OAuth consumer credentials can lure a logged-in administrator or customer to a crafted confirm URL that authorizes the attacker's request token, then exchange it at /oauth/token for a persistent REST API access token bound to the victim.3d