Vulnerabilities in pkg:npm/lightning-flow-scanner
PACKAGECVE-2025-67750 is a HIGH (CVSS 8.4) lightning flow scanner vulnerable to vulnerability (CWE-94: Improper Control of Generation of Code ('Code Injection')) affecting Lightning flow scanner libraries in the npm ecosystem. The issue involves lightning flow scanner vulnerable to code injection via unsafe use of `new function()` in apiversion rule. Remediation is available by upgrading affected packages to version 6.10.6.
pkg:npm/lightning-flow-scanner
Vulnerability advisories affecting package pkg:npm/lightning-flow-scanner. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-55jh-84jv-8mx8 | CVE-2025-67750 | HIGH | Lightning Flow Scanner Vulnerable to Code Injection via Unsafe Use of `new Function()` in APIVersion Rule |
CVE-2025-67750 at a Glance
Security Impact
CVSS: 8.4
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
How to Fix CVE-2025-67750
To remediate this vulnerability, upgrade all affected Lightning flow scanner dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install lightning-flow-scanner@6.10.6
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls lightning-flow-scanner
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2025-67750, inspect your project dependencies using npm:
npm ls lightning-flow-scanner
Analyze the terminal output to locate any version of Lightning flow scanner in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 6.10.6), your application is affected.
Note: The npm ls lightning-flow-scanner command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-94: Improper Control of Generation of Code ('Code Injection'), where 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. In Lightning flow scanner, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2025-67750 Affected Lightning flow scanner Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
lightning-flow-scanner
|
npm |
< 6.10.6
|
6.10.6
|
References
Frequently Asked Questions
What is CVE-2025-67750?
Which Lightning flow scanner versions are affected?
What version fixes CVE-2025-67750?
Is lightning-flow-scanner affected?
What is the CVSS score of CVE-2025-67750?
What CWE is associated with CVE-2025-67750?
How can I check npm dependencies for CVE-2025-67750?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-55jh-84jv-8mx8",
"modified" : "2025-12-20T05:00:37Z",
"published" : "2025-12-12T20:20:34Z",
"aliases" : [ "CVE-2025-67750" ],
"summary" : "Lightning Flow Scanner Vulnerable to Code Injection via Unsafe Use of `new Function()` in APIVersion Rule",
"details" : "### Impact\nThe APIVersion rule uses `new Function()` to evaluate expression strings. A malicious crafted flow metadata file can cause arbitrary JavaScript execution during scanning. An attacker could execute arbitrary JavaScript during a scan by supplying a malicious expression within rule configuration or crafted flow metadata. This could compromise developer machines, CI runners, or editor environments.\n\n### Patches\nThe patch removes all uses of `new Function()` and replaces them with a safer parser. It now validates operators (`>`, >=`, `<`, `<=`, `==`) and performs numeric comparisons without evaluating untrusted JavaScript.\n\n**version:** core-v6.10.6,\n**version vsx:**: v2.4.4\n**version app:**: v3.1.0\n\n### Work around\n\n```\n// --- Handle APIVersion rule separately to avoid unsafe-eval in the core library ---\n const apiVersionConfig = ruleConfig.rules.APIVersion;\n if (apiVersionConfig) {\n delete ruleConfig.rules.APIVersion;\n }\n\n// Manually evaluate the APIVersion rule, if it was configured.\n if (apiVersionConfig) {\n const flowApiVer = this.currentFlow.apiVersion || this.currentFlow.xmlData?.apiVersion;\n const apiVersionRuleDef = allRules.find(r => r.name === \"APIVersion\");\n\n // Determine the required expression (e.g. \">=58\").\n let requiredExpr;\n if (apiVersionConfig.expression) {\n requiredExpr = apiVersionConfig.expression;\n } else if (apiVersionConfig.threshold != null) {\n requiredExpr = `>=${apiVersionConfig.threshold}`;\n }\n\n if (requiredExpr) {\n const minVer = parseInt(requiredExpr.replace(/[^0-9]/g, \"\"), 10);\n const operator = requiredExpr.replace(/[0-9]/g, \"\").trim();\n const operators = {\n \">=\": (a, b) => a < b,\n \"<\": (a, b) => a >= b,\n \">\": (a, b) => a <= b,\n \"<=\": (a, b) => a > b,\n \"==\": (a, b) => a !== b,\n \"=\": (a, b) => a !== b\n };\n const violation = operators[operator] ? operators[operator](flowApiVer, minVer) : flowApiVer < minVer;\n\n if (violation) {\n // Craft a result object that mimics the core scanner output so downstream logic remains unchanged.\n const manualScanResult = [{\n flow: parsedFlow,\n ruleResults: [{\n ruleName: \"APIVersion\",\n ruleDefinition: {\n description: apiVersionRuleDef?.description || \"API Version check\",\n label: apiVersionRuleDef?.label || \"APIVersion\"\n },\n occurs: true,\n severity: apiVersionConfig.severity,\n details: [{\n name: String(flowApiVer),\n type: \"apiVersion\",\n expression: requiredExpr\n }]\n }]\n }];\n results.push(...this.processScanResults(manualScanResult));\n }\n }\n }\n\n```",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "lightning-flow-scanner"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "6.10.6"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/Flow-Scanner/lightning-flow-scanner/security/advisories/GHSA-55jh-84jv-8mx8"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-67750"
}, {
"type" : "WEB",
"url" : "https://github.com/Flow-Scanner/lightning-flow-scanner/commit/10f64a5eb193d8a777e453b25e910144e4540795"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/Flow-Scanner/lightning-flow-scanner"
}, {
"type" : "WEB",
"url" : "https://github.com/Flow-Scanner/lightning-flow-scanner/releases/tag/core-v6.10.6"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-94" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2025-12-12T20:20:34Z",
"nvd_published_at" : "2025-12-12T21:15:59Z"
}
}