https://feed.craftedsignal.io/tags/wekan/Trending threats, MITRE ATT&CK coverage, and detection metadata — refreshed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioThu, 23 Apr 2026 10:00:00 +0000https://feed.craftedsignal.io/briefs/2026-04-wekan-missing-auth/Thu, 23 Apr 2026 10:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-04-wekan-missing-auth/WeKan before 8.35 contains a missing authorization vulnerability in the Integration REST API endpoints, allowing authenticated board members to perform administrative actions without proper privilege verification, potentially leading to unauthorized data access and modification.WeKan, a collaborative Kanban board application, is vulnerable to a missing authorization issue in versions prior to 8.35. This flaw resides within the Integration REST API endpoints, where authenticated board members can execute administrative actions without sufficient privilege validation. An attacker, if they are an authenticated user, can exploit this vulnerability to enumerate integrations, including webhook URLs, create new integrations, modify or delete existing integrations, and manage integration activities. The root cause is insufficient authorization checks within the JsonRoutes REST handlers. Successful exploitation can lead to unauthorized access to sensitive information and modification of board configurations.

Attack Chain

1. An attacker gains valid credentials for a WeKan board member account.
2. The attacker authenticates to the WeKan application via the standard login procedure.
3. The attacker sends a crafted HTTP request to the /api/integration endpoint without proper administrative privileges.
4. Due to missing authorization checks, the request is processed, and the attacker is able to enumerate existing integrations, including sensitive webhook URLs.
5. The attacker crafts another HTTP request to the /api/integration endpoint to create a new, malicious integration (e.g., a webhook that sends data to an external attacker-controlled server).
6. The attacker modifies existing integrations to redirect data flow to attacker-controlled endpoints.
7. The attacker deletes legitimate integrations, disrupting board functionality.
8. The attacker manages integration activities, potentially triggering malicious actions or gaining further information.

Impact

Successful exploitation of this vulnerability allows an attacker to perform administrative actions on WeKan boards without proper authorization. This can lead to the exposure of sensitive webhook URLs, unauthorized modification or deletion of integrations, and the creation of malicious integrations for data exfiltration or disruption. The CVSS v3.1 score of 8.3 indicates a high severity vulnerability with significant potential for data compromise and system impact. The number of affected WeKan installations is currently unknown, but organizations using WeKan for project management and collaboration are at risk.

Recommendation

• Upgrade WeKan to version 8.35 or later to patch CVE-2026-41454, addressing the missing authorization vulnerability as detailed in the reference links.
• Deploy the Sigma rule “Detect WeKan Integration API Abuse” to identify potential exploitation attempts against the Integration REST API endpoints, monitoring webserver logs for unusual API requests.
• Review and restrict access rights for WeKan board members, ensuring that only authorized personnel have administrative privileges to minimize the attack surface as outlined in the overview.
• Monitor webserver logs for requests to /api/integration with methods like POST, PUT, and DELETE originating from non-admin users.

]]>highadvisorywekanmissing-authorizationrest-apiprivilege-escalationhttps://feed.craftedsignal.io/briefs/2024-01-02-wekan-ssrf/Tue, 02 Jan 2024 12:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-01-02-wekan-ssrf/WeKan before 8.35 is vulnerable to server-side request forgery (SSRF), allowing attackers with integration modification privileges to set webhook URLs to internal network addresses, leading to unauthorized HTTP POST requests and potential comment manipulation.WeKan, a popular open-source kanban board application, is susceptible to a server-side request forgery (SSRF) vulnerability in versions prior to 8.35. This flaw resides in the handling of webhook integration URLs, where insufficient validation allows attackers to specify arbitrary internal network addresses as webhook targets. An attacker with the ability to create or modify integrations within WeKan can exploit this vulnerability. By crafting a malicious webhook URL, they can force the WeKan server to issue HTTP POST requests to attacker-controlled internal targets, potentially exposing sensitive internal resources and data. This vulnerability can also be chained with another flaw to overwrite arbitrary comment text without authorization checks, increasing the potential for data manipulation and unauthorized access.

Attack Chain

1. An attacker gains access to a WeKan account with privileges to create or modify integrations.
2. The attacker navigates to the webhook integration settings within a WeKan board.
3. The attacker enters a malicious URL pointing to an internal server (e.g., http://internal.example.com/admin) in the webhook URL field.
4. The attacker triggers an event on the WeKan board (e.g., creating a new card, moving a card).
5. The WeKan server, without proper validation, sends an HTTP POST request to the attacker-specified internal URL.
6. The internal server receives the request, potentially revealing sensitive information about the WeKan board and its contents.
7. The attacker exploits response handling to overwrite arbitrary comment text without authorization checks.
8. The attacker gains unauthorized access to internal resources or sensitive data through the SSRF vulnerability.

Impact

Successful exploitation of this SSRF vulnerability allows attackers to potentially access internal network resources that are otherwise inaccessible from the outside. This could lead to the disclosure of sensitive information, such as internal application configurations, database credentials, or other confidential data. Furthermore, the ability to overwrite arbitrary comment text can be used to deface WeKan boards, spread misinformation, or disrupt normal operations. The CVSS v3.1 base score for this vulnerability is 8.5, indicating a high severity risk.

Recommendation

• Upgrade WeKan to version 8.35 or later to remediate CVE-2026-41455.
• Implement network segmentation to limit the impact of potential SSRF attacks.
• Deploy the Sigma rule DetectSuspiciousWekanWebhookUrls to identify attempts to exploit this vulnerability by monitoring for requests to internal IP addresses or unusual domains.
• Enable web server logging for the WeKan instance to capture details of outgoing HTTP requests.

]]>highadvisoryssrfwekancve-2026-41455