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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Multi-tenant mode is enabled (tenant.enable=true). The attacker holds a valid JWT from the normal tenant login.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 18/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fix or patch referenced
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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 whether your setup matches what the bug needs.
Multi-tenant mode is enabled (tenant.enable=true). The attacker holds a valid JWT from the normal tenant login.Apply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- madong-code madong-admin-saas
through 5.1.4
Evidence 4
- Patch
- Report
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120445
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: github.com
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: github.com
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: github.com
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: cve.now feed data