Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach platform tenant API over network
-
ExploitCall /platformapi/tenant/account unauthenticated
-
ExecutionCreate, modify or delete tenants and bind plans
-
ImpactFull tenant takeover and data manipulation
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No special conditions - remote unauthenticated exploitation against default configurations of madong-admin-saas through 5.1.4, because the shipped config/middleware.php registered the authentication middleware under the key 'platformapi' instead of the webman application name 'platform', so AccessTokenMiddleware was never applied to the platform tenant-management endpoints. The affected endpoints are /platformapi/tenant/account, /platformapi/tenant/bind-plan and /platformapi/tenant/sync-data. Limiting factors: the attacker must have network reachability to the platform API surface (an internet-exposed or otherwise accessible instance), and the deployed version must be at or below 5.1.4; applying the vendor fix removes access entirely for non-platform/root identities. |
| Impact | All exploitability signals point to an easy-to-trigger flaw: the CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes a remote, low-complexity, unauthenticated call with no user interaction, and the source diff confirms the mechanism - the middleware config used the key 'platformapi' (a route prefix) instead of the webman application name 'platform', so the platform application's AccessTokenMiddleware was never loaded and the tenant-management endpoints ran with no authentication at all. The high 8.8 score and the CWE-306 missing-authentication classification are therefore well supported by concrete evidence. However, the decision signals temper urgency: the vuln.today priority label is 'this_week', NOT act_now or emergency; no KEV listing is present (not confirmed actively exploited); no EPSS score was supplied, so exploitation probability cannot be quantified; and no verified working exploit code is referenced. The dominant mitigating factor is real-world footprint - madong-admin-saas is an obscure open-source project, so despite the severe, trivially exploitable defect, mass opportunistic exploitation is unlikely and this reads as a genuine but narrowly-scoped priority rather than an internet-wide emergency. Net: fix within the week as the vendor priority suggests, prioritized by whether any instance is actually internet-exposed. |
| Exploit ScenarioDerived | An unauthenticated attacker who can reach the application sends a request to /platformapi/tenant/account (or bind-plan / sync-data); because the platform application never loaded its AccessTokenMiddleware, the request is processed with no identity check, letting the attacker enumerate, create, modify, disable or delete tenants and bind subscription plans. No public exploit is identified at time of analysis, but the vulnerable endpoints and root cause are documented in the VulnCheck advisory and the vendor patch commit. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms this is a single low-complexity remote request with no prerequisites. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 02, 2026
Madong Admin SaaS through 5.1.4 exposes its platform tenant-management API without authentication because the shipped middleware configuration registers the platform access-token middleware under the key 'platformapi' instead of the webman application key 'platform', so calls to /platformapi/tenant/account, /platformapi/tenant/bind-plan and /platformapi/tenant/sync-data reach controller actions with no identity check. Remote unauthenticated attackers who can reach the platform API can therefore list, create, modify, disable or delete tenants and bind subscription plans. The vendor has published an upstream fix, the issue is high severity (CVSS 8.8), and no public exploit was identified at time of analysis.
RemediationAI
Apply the upstream vendor fix in commit 2a199a1523ed749c94b876bc2ae5fedf252b2e39 (https://github.com/madong-code/madong-admin-saas/commit/2a199a1523ed749c94b876bc2ae5fedf252b2e39); the supplied data confirms patch availability from the vendor but does not identify a tagged fixed release, so a released patched version is not independently confirmed. After updating, verify config/middleware.php registers the platform authentication middleware under the application key 'platform' rather than 'platformapi' and that AccessTokenMiddleware rejects requests whose JWT lacks a platform or root administrator type. If the patch cannot be applied immediately, restrict access to the platform API surface and specifically to /platformapi/tenant/account, /platformapi/tenant/bind-plan and /platformapi/tenant/sync-data at the reverse proxy or network boundary; the trade-off is that legitimate platform tenant administration is also blocked.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is CWE-306 (Missing Authentication for Critical Function) in a PHP webman-style application. webman selects middleware per application key, and the repository's config/middleware.php had 'platformapi' as the key for the platform middleware list; 'platformapi' is the route prefix, not the application name inferred from the app\platform controller namespace, so app\platform\middleware\AccessTokenMiddleware was never attached to the platform application's routes. The tenant controllers are implemented in app/platform/controller/tenant/AccountController.php, with the account endpoint at line 26, and the affected routes include /platformapi/tenant/account, /platformapi/tenant/bind-plan and /platformapi/tenant/sync-data. The supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H) and the independent CVSS 3.1 assessment (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H) agree that exploitation is remote, low-complexity and unauthenticated; the source diff confirms the fix changes the middleware key to 'platform' and makes AccessTokenMiddleware unconditionally require a platform or root administrator type.
Know when Madong Admin Saas gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Misconfigured middleware leaves the API unauthenticated (PR:N) over the network with a single low-complexity request (AC:L); tenant listing yields limited disclosure (C:L) while create/modify/delete gives high integrity and availability impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
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.
Executive ViewAI
CVE-2026-120446 is a critical authentication bypass in the Madong Admin SaaS platform (through version 5.1.4) that allows any unauthenticated network attacker to fully control the tenant management API, including creating, modifying, or deleting tenants and binding subscription plans. This vulnerability directly threatens the integrity and availability of the SaaS platform, enabling unauthorized access to sensitive tenant data and potential service disruption for all customers. Leadership must prioritize immediate remediation to prevent business disruption, data breaches, and reputational damage.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-115206
GHSA-rqh8-vfjg-c7gf
NVD
CVE.org
EPSS
Exploit-DB