https://feed.craftedsignal.io/tags/rest-api/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-mirofish-auth-bypass/Wed, 03 Jan 2024 12:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-01-mirofish-auth-bypass/A missing authentication vulnerability (CVE-2026-7042) exists in 666ghj MiroFish up to version 0.1.2, allowing remote attackers to bypass authentication via manipulation of the REST API Endpoint's create_app function.A critical authentication bypass vulnerability, tracked as CVE-2026-7042, has been identified in 666ghj MiroFish software up to version 0.1.2. The vulnerability lies within the create_app function of the backend/app/__init__.py file, which manages the REST API Endpoint. A remote attacker can exploit this flaw by manipulating specific parameters within API requests, effectively bypassing authentication mechanisms. This allows unauthorized access to sensitive functionalities and data. Public exploits are available, increasing the risk of widespread exploitation. The vendor was notified, but has not yet responded.

Attack Chain

1. The attacker identifies a vulnerable MiroFish instance running version 0.1.2 or earlier.
2. The attacker crafts a malicious HTTP request targeting the REST API Endpoint.
3. The crafted request manipulates parameters intended for the create_app function, specifically designed to bypass authentication checks.
4. The vulnerable create_app function fails to properly validate the request due to the missing authentication check.
5. The application grants unauthorized access to protected resources or functionalities.
6. The attacker performs unauthorized actions, such as data exfiltration, modification, or deletion, depending on the exposed API endpoints.
7. The attacker leverages the initial access to further compromise the system or pivot to other internal resources.

Impact

Successful exploitation of CVE-2026-7042 allows an attacker to bypass authentication controls in MiroFish applications. This can lead to unauthorized access to sensitive data, modification of application settings, or complete system compromise. The lack of authentication on the REST API endpoint can have severe implications for data confidentiality, integrity, and availability. Given the availability of a public exploit, affected organizations are at immediate risk.

Recommendation

• Monitor web server logs for suspicious HTTP requests targeting the REST API Endpoint with unusual parameters, using the provided Sigma rule that detects anomalous HTTP methods in webserver logs.
• Apply any available patches or updates from 666ghj to address CVE-2026-7042 immediately.
• Review the affected backend/app/__init__.py file for authentication logic flaws and implement necessary security measures.

]]>highadvisorycve-2026-7042authentication-bypassrest-api