Does this vulnerability allow full account takeover or arbitrary code execution?

No. The issue is limited to authorization around attachment uploads and object relationships; it does not directly provide credential theft or code execution, but it can affect where attachments are stored and associated.

What level of access does an attacker need to exploit this?

An attacker typically needs to be an authenticated WeKan user with the ability to reach the attachment upload API and craft custom requests. They do not need administrative permissions, but they must have some valid account.

What is the safest general fix pattern for this issue?

The safest pattern is to centralize authorization and relationship validation: derive the full target object hierarchy on the server from minimal identifiers, confirm it forms a valid relationship, and then verify that the authenticated user is permitted to perform attachment operations on that exact resource.

Severity:

HIGH RISK

(7.5)

Authorization Logic Weakness (CWE-863) in WeKan Attachment Upload API

CVE-2026-25561

Published:

Feb 7, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-306

CRITICAL RISK

CRITICAL

(9.8)

Missing Authentication for Forgot-Password Email Change API (CWE-306)

Account Takeover / Loss of Account Control

February 17, 2026

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in node-sonos-http-api TTS Provider for macOS

Remote Code Execution on the Server Host

February 17, 2026

Vulnerability Type

Category:

Authorization Logic Flaw

CWE:

CWE-863

Impact:

Unauthorized Data Access / Integrity Impact

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Vulnerability Type

Category:

Authorization Logic Flaw

CWE:

CWE-863

Impact:

Unauthorized Data Access / Integrity Impact

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Authorization Logic Weakness (CWE-863) in WeKan Attachment Upload API

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

CRITICAL RISK

CRITICAL

(9.8)

Missing Authentication for Forgot-Password Email Change API (CWE-306)

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in node-sonos-http-api TTS Provider for macOS

Vulnerability Type

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare