All vulnerabilities

Servers and applications

GHSA-xvh8-793v-rp59

PATCH /api/v3/meeting_outcomes/:id can move another user's outcome out of a meeting the caller may only view: the contract checks manage_outcomes on the new agenda item only

Severity
Medium
Published
19 Nov 2026
Last changed
19 Nov 2026
Added to UpHeron
19 Nov 2026
Fixed in
17.9.8
Weakness
Incorrect authorization (CWE-863)
Sources
Project advisories (GitHub)

Description

The meeting outcome API accepts _links.agendaItem on update, and the outcome contract (MeetingOutcomes::EditableItem) checks manage_outcomes, editability and the backlog state on model.meeting_agenda_item after the new attributes have been set, i.e. on the destination agenda item only. Nothing checks the agenda item the outcome currently belongs to. The endpoint itself only requires that the outcome's meeting is visible (Meeting.visible). A user who has view_meetings in project A and manage_outcomes in project B can therefore send one PATCH that moves an outcome of a meeting in A (including a closed meeting) to an in-progress agenda item of a meeting in B, and then rewrite or delete it there. The outcome disappears from A's meeting and cannot be moved back without manage_outcomes in A. The agenda item contract already does this check for moving agenda items between meetings (user_allowed_to_edit_in_source_project).

From opf/openproject's security advisory. Shortened; the full text is there.

Affected software

SoftwareAffected versions
OpenProjectServers and applications · github:opf/openproject
  • Every version before 17.9.8

About OpenProject

web-based project management system

From Wikidata, CC0 1.0.
Total downloads
30M+OpenProject
Docker Hub pulls
6,225,306Docker Hub, 15 Nov 2026
GitHub stars
17,385GitHub, 15 Nov 2026
Forks
3,765GitHub, 15 Nov 2026
Latest release
v17.9.7GitHub, 15 Nov 2026
Released
9 Nov 2026GitHub
License
GNU General Public License, version 3.0Wikidata
Written in
RubyWikidata
First published on GitHub
28 Nov 2012GitHub

References