/

CVE-2026-75419

Severity:

HIGH RISK

(8.8)

Missing Authorization (CWE-113) in GoWind CMS Admin

CVE-2026-75419

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-113

Impact:

Unauthorized Administrative Actions

Severity:

HIGH RISK

(8.8)

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.

Summary

GoWind CMS before 1.0.0 contains a missing authorization vulnerability in its administrative service. Because the authorization engine performs no effective role or tenant checks, any authenticated user may invoke sensitive administrative APIs, including user deletion, password resets, and tenant creation.

Affected context

The issue occurs in GoWind CMS deployments where the administrative and application services use the affected NewAuthorizer() implementation. That function returns a no-op authorization state, allowing authenticated requests to reach administrative operations without effective role-based or tenant-scoped authorization checks.

Exploit preconditions

  • Attack surface: Authenticated administrative and application API endpoints
  • Required access: Any valid authenticated user account
  • Trigger point: Invocation of an administrative API operation
  • Why exploitation is possible: The authorization middleware uses a no-op engine and does not enforce the caller's role or tenant permissions

Why this happens

The underlying bug is an authorization enforcement failure. NewAuthorizer() returns a no-op authorization implementation, causing middleware checks to allow requests rather than evaluate roles, permissions, or tenant boundaries. This behavior is consistent with missing authorization controls, although the supplied CWE-113 identifier is associated with HTTP response splitting and may not precisely describe the authorization defect.

Potential impact

  • An authenticated user may delete other users
  • An attacker could reset account passwords
  • Unauthorized tenants could be created
  • Tenant isolation may be weakened or bypassed
  • Administrative data and configuration may be modified
  • The application could suffer service disruption or broader compromise

General mitigation guidance

Mitigation generally focuses on making authorization mandatory, explicit, and fail-closed.

Common defensive patterns include:

  • Replace no-op authorization implementations with policy-enforcing authorization services
  • Apply role and tenant checks independently at every sensitive operation boundary
  • Deny access by default when authorization state is missing, invalid, or unavailable
  • Derive authorization decisions from trusted server-side identity and tenant context rather than client-controlled values
  • Limit administrative capabilities through least-privilege roles and narrowly scoped service accounts
  • Centralize policy definitions while retaining operation-level enforcement for defense in depth

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis rules that flag no-op authorization providers, unconditional allow results, and empty policy implementations
  • Code review checks for administrative handlers lacking explicit permission and tenant validation
  • Integration tests that exercise sensitive APIs with users from different roles and tenants
  • Runtime audit logging and policy monitoring for administrative actions performed by non-privileged accounts
  • CI policy enforcement requiring authorization tests for user-management, credential, and tenant-management endpoints

Automated security review tools may help identify authorization middleware that always permits requests.

Sources

SourceLink
github.comgithub.com/TKar0/TKar0-CvePoc/tree/main/2026-CVE-POC/CVE-2026-75419
github.comgithub.com/tx7do/go-wind-cms/issues/23

Frequently asked

questions

Any authenticated user may be able to invoke affected administrative APIs, regardless of assigned role or tenant, when the vulnerable authorization path is active.

No. The described condition requires a valid authenticated account, but it does not require administrative privileges.

Replace the no-op authorization engine with fail-closed, server-side policy enforcement that validates both operation permissions and tenant scope.

Use least-privilege roles, test authorization across role and tenant boundaries, review sensitive endpoints for explicit checks, and monitor administrative actions.

Find out what's already
exploitable in your codebase.