Choseogyeong

**Name of the Vulnerable Software and Affected Versions** PraisonAI versions prior to 4.5.133 **Description** An SQL identifier injection exists in SQLiteConversationStore where the `table prefix` configuration value is directly concatenated into SQL queries using f-strings without validation or sanitization. Because SQL identifiers cannot be safely parameterized, an attacker who can influence the `table prefix` value through configuration inputs such as `from yaml` or `from dict` can inject arbitrary SQL fragments. This allows for the alteration of query structures, enabling unauthorized data access, such as reading internal SQLite tables like `sqlite master`, and the manipulation of query results through techniques like UNION-based injection. The issue originates in `config.py`, propagates through `factory.py` via the `create stores from config` function, and reaches the sink in `sqlite.py`. **Recommendations** Update to version 4.5.133.

**Name of the Vulnerable Software and Affected Versions** wenxian versions 0.3.1 and earlier **Description** wenxian is a tool used to generate BIBTEX files from identifiers such as DOI, PMID, arXiv ID, or paper titles. A GitHub Actions workflow in the software uses untrusted user input from the `issue comment.body` variable directly within a shell command. Because the input is interpolated without sanitization, it allows for command injection, enabling remote attackers to execute arbitrary code on the runner. This could lead to the compromise of the CI/CD pipeline, exfiltration of repository data, and unauthorized access to the `GITHUB TOKEN`. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability. Avoid directly interpolating untrusted user input into shell commands by passing `issue comment.body` through an environment variable and referencing it safely within the script.