FKIE_CVE-2026-48483
Vulnerability from fkie_nvd - Published: 2026-08-11 17:18 - Updated: 2026-10-23 19:10| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"product": "typebot.io",
"vendor": "baptisteArno",
"versions": [
{
"status": "affected",
"version": "\u003c 3.17.0"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "TypeBot is a chatbot builder tool. Prior to version 3.17.0, Typebot\u0027s WhatsApp status forwarding feature stores a workspace-configured webhook forwarding URL and later POSTs WhatsApp marketing/error status events to it from the server. The stored URL is only validated as a generic URL in settings, but the forwarding code uses the raw `ky` instance instead of the repository\u0027s SSRF-protected `safeKy` client. A workspace user who can configure WhatsApp settings can therefore make the Typebot server issue HTTP requests to internal services, private-network hosts, localhost, or metadata-style endpoints whenever the public WhatsApp production webhook receives a status payload that should be forwarded. Version 3.17.0 patches the issue."
},
{
"lang": "es",
"value": "TypeBot es una herramienta de creaci\u00f3n de chatbots. Antes de la versi\u00f3n 3.17.0, la funci\u00f3n de reenv\u00edo de estado de WhatsApp de Typebot almacena una URL de reenv\u00edo de webhook configurada por el espacio de trabajo y posteriormente env\u00eda eventos de estado de marketing/error de WhatsApp a ella desde el servidor. La URL almacenada solo se valida como una URL gen\u00e9rica en la configuraci\u00f3n, pero el c\u00f3digo de reenv\u00edo utiliza la instancia \u2019ky\u2019 sin procesar en lugar del cliente \u2019safeKy\u2019 protegido contra SSRF del repositorio. Un usuario del espacio de trabajo que puede configurar los ajustes de WhatsApp puede, por lo tanto, hacer que el servidor de Typebot emita solicitudes HTTP a servicios internos, hosts de red privada, localhost o puntos finales de estilo metadatos cada vez que el webhook de producci\u00f3n p\u00fablico de WhatsApp reciba una carga \u00fatil de estado que deba ser reenviada. La versi\u00f3n 3.17.0 corrige el problema."
}
],
"id": "CVE-2026-48483",
"lastModified": "2026-10-23T19:10:00.167",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.4,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 2.5,
"source": "security-advisories@github.com",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-48483",
"options": [
{
"exploitation": "poc"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-08-11T18:34:06.275082Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-08-11T17:18:02.067",
"references": [
{
"source": "security-advisories@github.com",
"url": "https://github.com/baptisteArno/typebot.io/commit/30cbc616e00efabb193c3221b36a0d417152592c"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/baptisteArno/typebot.io/pull/2497"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/baptisteArno/typebot.io/releases/tag/v3.17.0"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/baptisteArno/typebot.io/security/advisories/GHSA-5c92-7q58-4rgx"
},
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"url": "https://github.com/baptisteArno/typebot.io/security/advisories/GHSA-5c92-7q58-4rgx"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-918"
}
],
"source": "security-advisories@github.com",
"type": "Secondary"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.