T05 · Unauthorized Access and Privilege Escalation
- Location
index.ts:56- Finding
Ambiguous Session Resolution Enables Cross-Session Transcript Access and Replacement
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This save/load plugin does what it says, but it can expose or replace conversation history because session scoping and saved transcript handling are too loose.
Install only if you are comfortable with full conversations being saved locally in plaintext and restored into future agent context. Avoid using it in shared OpenClaw installations or multi-user gateways until session ownership checks, restrictive file permissions, confirmation for destructive actions, and safer context restoration are added.
index.ts:56Ambiguous Session Resolution Enables Cross-Session Transcript Access and Replacement
index.ts:523Saved Conversation Content Is Injected into a Privileged System Event
index.ts:374Sensitive Conversation Transcripts Are Persisted Without Explicit Restrictive Permissions
The documented description is narrower than the actual described behavior: beyond basic save/load, the skill also supports permanent deletion, session transcript rewriting, and system event injection that can influence subsequent agent behavior. That mismatch is dangerous because users and reviewers may grant trust based on a benign-looking summary while missing capabilities that alter state, destroy data, or create an indirect prompt-injection channel through injected file-path context.
Referenced artifact was not completely inspected
2. Ensure `openclaw.plugin.json` and `package.json` are present
The skill persists conversation history to disk but does not clearly warn that saved transcripts may contain secrets, personal data, tokens, or other sensitive content. In this context, the omission materially increases the chance of accidental data exposure because users may assume chat context is ephemeral while the plugin creates durable local files that can later be accessed, copied, or backed up.
Documenting a permanent deletion command without an explicit warning or confirmation expectation makes accidental destructive use more likely. In a context-management skill, deleting saved conversations can cause irreversible loss of audit trail, work product, or evidence of prior interactions, especially if users invoke commands by label or index and make selection mistakes.
The load command archives the current transcript and writes a new transcript file to replace the active session context. Although the code performs the action as part of loading, there is no user-facing warning in the command description or an explicit confirmation that current session state will be replaced and archived.
The plugin injects a system event instructing the agent to read the full saved file and 'continue the conversation naturally, as if you remember everything.' Because save files contain prior user/assistant messages and the prompt explicitly causes the agent to internalize them, previously stored sensitive data can be reintroduced into the model context and influence future outputs, potentially disclosing prior conversation content across turns or to the wrong audience if session resolution is incorrect.
The delete path unlinks the save file from disk and removes its index entry, which is a destructive operation. The command metadata and surrounding user guidance do not clearly warn that /load --delete permanently deletes saved context, and there is no confirmation prompt before deletion.
The manifest describes the skill only as "Save and load conversation context to file," but provides no specific trigger phrases, scope limits, or exclusion conditions. In a manifest file, this kind of generic capability description can overlap with common requests about saving or loading context and may cause unintended invocation.
The manifest explicitly says the skill saves and loads conversation context to file, but provides no user-facing warning about persistence, retention, or sensitivity of stored data. Because conversation context can contain secrets, personal data, or proprietary information, silent or poorly disclosed file storage increases the risk of unintended data exposure on disk or later recovery by other users/processes.
The skill emits some user-facing messages in Chinese while command descriptions and other responses are in English. This imposes a language choice on users without opt-in or documentation that the skill is intended for a Chinese-speaking context.
Dependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.