clawvet self-hosted API server (apps/api) before 0.7.5 hard-codes a fallback JWT secret ('clawvet-dev-secret-change-me') in auth.ts and ships it as the default in .env.example. Because GET /api/v1/scans returns scan records containing userId values without authentication, a remote unauthenticated attacker can harvest a victim's userId, forge a valid HS256 cg_session cookie offline using the known secret, and call GET /api/v1/auth/me to obtain the victim's email address, subscription plan, and secret apiKey. The published clawvet npm package (CLI only) is not affected.
Security readout for executives and security teams
Plain-English summary
A flaw in clawvet’s self-hosted API can let an unauthenticated remote attacker impersonate users and access sensitive account data, including email addresses, subscription details, and API keys. The issue combines exposed user identifiers with a predictable JWT signing secret. The CLI-only npm package is not affected.
Executive priority
Treat internet-accessible or default-configured deployments as an immediate remediation priority. The vulnerability can expose reusable API credentials and enable account impersonation without victim interaction. Upgrade, rotate secrets and API keys, invalidate sessions, and investigate possible misuse. CLI-only installations do not require action for this CVE.
Technical view
Before version 0.7.5, clawvet’s apps/api server uses a hard-coded fallback JWT secret also published in its example environment configuration. An unauthenticated scans endpoint exposes user identifiers, enabling offline creation of trusted HS256 session cookies. These sessions can access the authentication profile endpoint and disclose victim account information and API keys.
Likely exposure
Self-hosted clawvet API deployments running versions earlier than 0.7.5 are affected, particularly when remotely reachable and using the fallback or documented default secret. Deployments containing only the published CLI npm package are not affected. The supplied evidence does not establish how many vulnerable servers are publicly accessible.
Exploitation context
Exploitation is remotely feasible without authentication, privileges, or user interaction, according to the supplied advisories. The attack can compromise confidentiality and integrity but is not described as affecting availability. This CVE is not listed as KEV, and the supplied sources do not confirm active exploitation in the wild.
Researcher notes
The reported chain depends on two weaknesses: unauthenticated disclosure of user identifiers and a known symmetric JWT secret. Assessment should distinguish the self-hosted apps/api server from the unaffected CLI package. The supplied CVSS 4.0 score is 9.3. No CPEs, public exploitation confirmation, or deployment-prevalence data were provided.
Mitigation direction
Upgrade the self-hosted clawvet API server to version 0.7.5 or later.
Replace any fallback or example JWT secret with a unique, securely generated secret.
Invalidate existing sessions after changing the JWT signing secret.
Rotate potentially exposed API keys and investigate their prior use.
Review the vendor advisory for additional remediation guidance.
Validation and detection
Inventory deployments and confirm whether the self-hosted apps/api component is present.
Verify every deployed API server reports version 0.7.5 or later.
Confirm production configuration does not use the fallback or example JWT secret.
Test that scan records and user identifiers are not exposed without authorization.
Review logs for suspicious session activity and unexpected API-key use.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-306 · source CWE mapping
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Use of Hard-coded Cryptographic Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.