GHSA-XQG5-G7CJ-F6X6
Vulnerability from github – Published: 2026-11-05 15:32 – Updated: 2026-11-05 18:32Incorrect 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.
{
"affected": [],
"aliases": [
"CVE-2026-84728"
],
"database_specific": {
"cwe_ids": [
"CWE-863"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-05T14:17:07Z",
"severity": "MODERATE"
},
"details": "Incorrect Authorization in Apache OFBiz \n24.09 before 24.09.08 on all platforms, when documented multitenancy is \nenabled, allows a remote authenticated attacker holding only a valid \nlow-privilege account in one tenant to read and write data belonging to a\n different tenant, by submitting their own tenant\u0027s userTenantId \nalongside their own credentials to the normal Party Manager login \nagainst a hostname mapped to a different tenant: ContextFilter resolves \nthe tenant from the hostname via TenantDomainName, but LoginWorker gives\n priority to the conflicting userTenantId request parameter and \nauthenticates against the attacker\u0027s own tenant, so a subsequent \nordinary request to the same hostname combines the hostname-mapped \ntenant\u0027s Entity Engine delegator with the attacker\u0027s tenant\u0027s session \ndispatcher, security object, and identity, letting the permission check \nrun against the attacker\u0027s own tenant while the resulting read or write \nis performed against the hostname-mapped tenant\u0027s data. Users are \nrecommended to upgrade to version 24.09.08, which fixes this issue.",
"id": "GHSA-xqg5-g7cj-f6x6",
"modified": "2026-11-05T18:32:19Z",
"published": "2026-11-05T15:32:37Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-84728"
},
{
"type": "WEB",
"url": "https://lists.apache.org/thread.html/7b2syzksp7klt9fvhdg0olldvs2g83lz"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.