mitre / mitre/secure-coding-case-studies

LLM Plugin Injection

Open
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
11
Forks
45
PR merge metrics
No merged PRs in 30d

Description

LLM Plugin Injection is a vulnerability that takes place when untrusted input (eg, text, metadata, documents) contains hidden instructions or code that causes manipulation in the language model to perform malicious activity via APIs or plugins. LLMs interpret natural language as commands, and this is exploited by malicious actors where input can override system rules, causing data leaks, unauthorized access, and even remote code execution.

I propose adding a case study on this vulnerability unless there are any objections. As we live in the age of LLMs and broadly AI models, where such a vulnerability risks the exposure of sensitive files, unauthorized execution of functions in applications using LLMs, and primarily automation misuse, it is highly valuable.

References:
https://nvd.nist.gov/vuln/detail/CVE-2025-25362
https://www.hacktivesecurity.com/blog/2025/04/01/cve-2025-25362-old-vulnerabilities-new-victims-breaking-llm-prompts-with-ssti/

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue proposes a case study about LLM plugin injection and provides NVD and Hacktive Security references, but it names no repository files or tests. Start by reviewing the repository's existing case-study structure and the cited vulnerability details. Done means a complete case study is added in the project's established format and accurately explains the vulnerability and mitigation considerations.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, security
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.