Authenticated internal service access via unvalidated webhook URLs
Published Apr 22, 2026 · Updated Apr 22, 2026
Server-side request forgery in WeKan before 8.35 allows remote authenticated users to send board event data to internal services. The integration URL schema accepts arbitrary schemes and destinations, and outgoing.js posts full event payloads without rejecting private or loopback targets. Board members able to create or modify integrations can reach internal services; two-way response handling also permits unauthorized comment-text overwrite.
Summary
What happened
Server-side request forgery in WeKan before 8.35 allows remote authenticated users to send board event data to internal services. The integration URL schema accepts arbitrary schemes and destinations, and outgoing.js posts full event payloads without rejecting private or loopback targets. Board members able to create or modify integrations can reach internal services; two-way response handling also permits unauthorized comment-text overwrite.
The record
- CVE
- CVE-2026-41455
- Published
- Apr 22, 2026
- Updated
- Apr 22, 2026
- Vendor
- WeKan
- Product
- WeKan
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 22, 2026CVE publishedPublication date reported by the CVE source.
- Apr 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <8.35.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo