# CVE-2026-30844: Wekan Vulnerable to SSRF through Lack of Validation or Filtering in Attachment URL Loading

> Authenticated users can trigger SSRF via attachment URLs during board imports, allowing access to internal network services and sensitive metadata.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Mar 2026
- **Updated:** 9 Mar 2026

## What is CVE-2026-30844?

CVE-2026-30844 is a critical server-side request forgery vulnerability in Wekan, published on 6 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Wekan is an open source kanban tool built with Meteor. Versions 8.32 and 8.33 are vulnerable to Server-Side Request Forgery (SSRF) via attachment URL loading. During board import in Wekan, attachment URLs from user-supplied JSON data are fetched directly by the server without any URL validation or filtering, affecting both the Wekan and Trello import flows. The parseActivities() and parseActions() methods extract user-controlled attachment URLs, which are then passed directly to Attachments.load() for download with no sanitization. This Server-Side Request Forgery (SSRF) vulnerability allows any authenticated user to make the server issue arbitrary HTTP requests, potentially accessing internal network services such as cloud instance metadata endpoints (exposing IAM credentials), internal databases, and admin panels that are otherwise unreachable from outside the network. This issue has been fixed in version 8.34.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-30844?

It affects 1 product.


Products: Wekan Project Wekan.

## How do I fix CVE-2026-30844?

No fix has been published for CVE-2026-30844 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-30844 being exploited?

There is no known exploitation of CVE-2026-30844 in the wild and no public exploit code.

## Other vulnerabilities in Wekan

- [CVE-2026-30843](https://insights.sbomify.com/CVE-2026-30843/): Wekan has Cross-Board IDOR in Custom Fields Update Endpoints (critical 9.3)
- [CVE-2026-30847](https://insights.sbomify.com/CVE-2026-30847/): Wekan Credential Leak via notificationUsers Publication Exposes Password Hashes and Session Tokens (critical 9.3)
- [CVE-2025-65780](https://insights.sbomify.com/CVE-2025-65780/): Missing authorization in n/a (high 8.8)
- [CVE-2026-30846](https://insights.sbomify.com/CVE-2026-30846/): Wekan Exposes All Global Webhook Integrations through globalwebhooks Publication (high 8.7)
- [CVE-2026-25560](https://insights.sbomify.com/CVE-2026-25560/): WeKan < 8.19 LDAP Authentication Filter Injection (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-30844 and fix it if it is affected.

What it is: CVE-2026-30844 is a critical server-side request forgery vulnerability in Wekan, published on 6 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-30844 in the wild and no public exploit code.

Affected product: Wekan. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-30844/ (Markdown: https://insights.sbomify.com/CVE-2026-30844/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-30844
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-30844
- OSV: https://osv.dev/vulnerability/CVE-2026-30844

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-30844/
Summaries are generated and may contain mistakes; the official description above is the record.