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.
Severity
CVSS 3.1
5.4 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS
0.5%(up from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 45th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Show the promptExplain CVE-2026-84728 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-84728?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-84728?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-84728 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown: