AGORA PROJECT · CVE-2026-63164 · Other
NO FIX YET · SEE WHAT TO DO
Omnispace Agora Project through 26.10.0 fails to check mail ownership when a crafted reloadMailTypeId parameter is supplied to Ctrl::getCurObj() in CtrlMail.php. An logged-in attacker can read the title and body of other users' private messages.
first public Nov 13, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Self-hosted Omnispace Agora Project instances running 26.10.0 or earlier, where several users share one instance and use the Mail module. Any logged-in user can read other users' private mail title and body by changing the mail id. Single-user instances, or ones without the Mail module in use, are lower risk.
Not affected if auth-required
Who cares idor, omnispace-agora, php, self-hosted
26.10.0 are listed as affected26.10.5 fixes it is unconfirmed: the release notes don't say26.10.5 (https://github.com/xech/agora-project/releases) but its notes don't mention this issueOmnispace Agora Project through 26.10.0 contains an insecure direct object reference vulnerability that allows authenticated attackers to access another user's private mail by supplying a crafted reloadMailTypeId parameter to Ctrl::getCurObj() without a readRight() ownership check in CtrlMail.php. Attackers can manipulate the mail identifier value, such as reloadMailTypeId=mail-1, to retrieve the title and body of private messages belonging to other users, resulting in unauthorized disclosure of sensitive communications.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.