Token Optimizer MCP measures token savings per AI coding agent, optimizes context, and shares a live local knowledge graph across 16 CLI clients. Prior to version 5.1.0, the dashboard HTTP server in token-optimizer-mcp exposes /api/session-summary and /api/session-events with no authentication middleware — any network-accessible client can reach them without credentials. Both handlers concatenate the caller-supplied sessionId query parameter directly into a filesystem path via path.join, and Node.js normalizes .. segments at resolution time, allowing an unauthenticated attacker to read any .jsonl file reachable from the server's filesystem.
This issue has been patched in version 5.1.0.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
Low
Partial data leak
Integrity
None
No data modification
Availability
None
No disruption
CVSS Vector v3.1
Weakness Type (CWE)
Vulnerable Products
ooples:token-optimizer-mcp
References 3
https://github.com/ooples/token-optimizer-mcp/commit/b4ee96dac799cbfba0a9f9c178…
security-advisories@github.com
https://github.com/ooples/token-optimizer-mcp/releases/tag/v5.1.0
security-advisories@github.com
https://github.com/ooples/token-optimizer-mcp/security/advisories/GHSA-76pc-mqx…
security-advisories@github.com