Impact
From Wekan 8.36 to 9.74, the outgoing webhook URL validator only checked the literal hostname against a regular expression, failing to block DNS names that resolved to internal or blocked IPs. The flaw allows an attacker to supply a DNS‑resolved hostname that maps to an internal address, bypassing the SSRF guard and enabling the server to send arbitrary requests within the network. The vulnerability is a Remote Server‑Side Request Forgery, with an impact on confidentiality and integrity of internal resources.
Affected Systems
Wekan 8.36 through 9.74, deployed on Meteor, are affected. The issue occurs when the outgoing webhook integration URL is validated only against a hostname regular expression, which fails to thwart DNS hostnames that resolve to internal or blocked IPs.
Risk and Exploitability
The CVSS score of 8.5 classifies the issue as High severity, and the EPSS score is not available, indicating that publicly available data on exploitation frequency is lacking. The vulnerability is not entered in CISA’s KEV catalog. Successful exploitation requires creating or editing an outgoing webhook event in Wekan to point at a DNS name that resolves to a target internal address; no additional privileges or network reachability assumptions beyond the ability to configure webhooks are noted. The attack vector is therefore likely through the web application, making the flaw readily exploitable by users who can configure webhooks.
OpenCVE Enrichment