CVE-2026-84728: Apache OFBiz: Cross-tenant authorization bypass in mapped-domain login
Incorrect Authorization in Apache OFBiz 24.09 before 24.09.08 on all platforms, when documented multitenancy is enabled, allows a remote authenticated attacker holding only a valid low-privilege account in one tenant to read and write data belonging to a different tenant, by submitting their own tenant's userTenantId alongside their own credentials to the normal Party Manager login against a hostname mapped to a different tenant: ContextFilter resolves the tenant from the hostname via TenantDomainName, but LoginWorker gives priority to the conflicting userTenantId request parameter and authenticates against the attacker's own tenant, so a subsequent ordinary request to the same hostname combines the hostname-mapped tenant's Entity Engine delegator with the attacker's tenant's session dispatcher, security object, and identity, letting the permission check run against the attacker's own tenant while the resulting read or write is performed against the hostname-mapped tenant's data. Users are recommended to upgrade to version 24.09.08, which fixes this issue.
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache OFBizto a version that resolves this vulnerability.Fixed in 24.09.08
Event History
Frequently Asked Questions
Which deployments are affected?
Apache OFBiz 24.09 releases before 24.09.08 are affected only when documented multitenancy is enabled and hostnames are mapped to tenants through TenantDomainName. The issue applies on all platforms.
What access does an attacker need?
An attacker needs remote access and valid credentials for a low-privilege account in any one tenant. No user interaction is required.
What data can be accessed or changed?
The attacker can read and write data belonging to a different tenant by logging in through the normal Party Manager login on that tenant's mapped hostname while supplying their own tenant's userTenantId with their credentials.
How can this be remediated?
Upgrade Apache OFBiz to version 24.09.08, which fixes the authorization bypass.