{"id":"CVE-2026-115400","kind":"vulnerability","aliases":["CVE-2026-115400"],"related":[],"title":"crawlseo: Google OAuth refresh tokens stored in plaintext in database","description":"crawlseo before version 0.2.5 contains a cleartext storage vulnerability that allows attackers with database read access to obtain Google OAuth access and refresh tokens stored unencrypted in the User.googleTokens column. Attackers can read the plaintext long-lived refresh tokens from a compromised or exposed Postgres database to gain indefinite, unauthenticated access to all registered users' Google Search Console data.","summary":"crawlseo stores users' Google OAuth access and refresh tokens unencrypted in the User.googleTokens database column. Anyone who can read that Postgres database can take the long-lived refresh tokens and access every registered user's Google Search Console data.","severity":"medium","cvss":6.7,"epss":0.00087,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["crawlseo","google-search-console","package","postgres","self-hosted"],"not_affected_if":["no-google-oauth-connected","version-0.2.5-or-later"],"how_to_check":"- Check the installed crawlseo version with `npm ls crawlseo` or the project's package.json; versions below `0.2.5` are affected.\n- Look for a `googleTokens` column on the `User` table in the Postgres database (for example `\\d \"User\"` in psql) and see whether the stored values are readable plaintext tokens.","fix":"- Upgrade crawlseo to `0.2.5` or later.\n- Revoke existing Google OAuth grants for affected users and have them reconnect, since the old refresh tokens may already be exposed.\n- Restrict database read access to the crawlseo Postgres database to the application only.","status":"open","published_at":"2026-10-22T14:17:39+00:00","first_seen_at":"2026-10-23T21:57:31+00:00","triaged_at":"2026-10-25T03:45:23+00:00","updated_at":"2026-10-25T03:45:23+00:00","category":"package","confidence":0.7,"triage":{"at":"2026-10-25T03:45:23Z","model":"claude-haiku-5-5","output":{"fix":"- Upgrade crawlseo to `0.2.5` or later.\n- Revoke existing Google OAuth grants for affected users and have them reconnect, since the old refresh tokens may already be exposed.\n- Restrict database read access to the crawlseo Postgres database to the application only.","reach":"unknown","title":"crawlseo: Google OAuth refresh tokens stored in plaintext in database","impact":"medium","summary":"crawlseo stores users' Google OAuth access and refresh tokens unencrypted in the User.googleTokens database column. Anyone who can read that Postgres database can take the long-lived refresh tokens and access every registered user's Google Search Console data.","category":"package","nicknames":[],"who_cares":["crawlseo","google-search-console","postgres","self-hosted"],"confidence":0.7,"needs_auth":"yes","worst_case":"Attacker reads long-lived Google refresh tokens and accesses Search Console data indefinitely","analyst_note":"","how_to_check":"- Check the installed crawlseo version with `npm ls crawlseo` or the project's package.json; versions below `0.2.5` are affected.\n- Look for a `googleTokens` column on the `User` table in the Postgres database (for example `\\d \"User\"` in psql) and see whether the stored values are readable plaintext tokens.","needs_analyst":false,"not_affected_if":["version-0.2.5-or-later","no-google-oauth-connected"],"who_is_affected":"Teams that run crawlseo before `0.2.5` with Google Search Console connected for their users. Exposure depends on who can read the Postgres database, so a database reachable by other services, backups or a compromised host raises the risk. Deployments on `0.2.5` or later, or without Google connections, can skip it.","user_interaction":"no","needs_special_setup":"unknown","severity_if_unknown":"medium"},"cost_usd":0.000664,"input_tokens":3396,"output_tokens":648,"severity_before":"medium"},"analyst_status":null,"analyst_note":null,"search":"'-115400':13A,16A '-2026':12A,15A '0.2.5':70C 'access':32B,58B,82C,87C,118C 'allow':77C 'anyon':42B 'attack':78C,97C 'cleartext':73C 'column':41B,96C 'compromis':109C 'consol':21B,65B,125C 'contain':71C 'crawlseo':1A,17B,27B,67C 'cve':11A,14A 'data':66B,126C 'databas':10A,40B,48B,80C,113C 'everi':59B 'expos':111C 'gain':115C 'googl':2A,19B,30B,63B,85C,123C 'google-search-consol':18B 'host':26B 'indefinit':116C 'live':54B,104C 'long':53B,103C 'long-liv':52B,102C 'oauth':3A,31B,86C 'obtain':84C 'packag':22B 'plaintext':8A,101C 'postgr':23B,47B,112C 'read':45B,81C,99C 'refresh':4A,34B,55B,89C,105C 'regist':60B,121C 'search':20B,64B,124C 'self':25B 'self-host':24B 'storag':74C 'store':6A,28B,91C 'take':50B 'token':5A,35B,56B,90C,106C 'unauthent':117C 'unencrypt':36B,92C 'user':29B,61B,122C 'user.googletokens':39B,95C 'version':69C 'vulner':75C","nicknames":[],"mitigations":[],"who_affected":"Teams that run crawlseo before `0.2.5` with Google Search Console connected for their users. Exposure depends on who can read the Postgres database, so a database reachable by other services, backups or a compromised host raises the risk. Deployments on `0.2.5` or later, or without Google connections, can skip it.","tier":"C","verified":{},"analyst_revisit_at":null,"first_public_at":"2026-10-22T14:17:39+00:00","kev":null,"cvss_vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","cvss_by":"disclosure@vulncheck.com","poc_count":0,"sources":[{"source":"nvd","external_id":"CVE-2026-115400","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-115400","severity":null,"published_at":"2026-10-22T14:17:39+00:00","modified_at":"2026-10-22T17:40:46+00:00","first_seen_at":"2026-10-23T21:57:31+00:00","fetched_at":"2026-10-23T22:29:02+00:00","note":null},{"source":"epss","external_id":"CVE-2026-115400","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-115400","severity":null,"published_at":null,"modified_at":null,"first_seen_at":"2026-10-24T07:15:51+00:00","fetched_at":"2026-10-24T07:15:51+00:00","note":null}],"documents":[],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}