CIVI-SA-2026-29: Multiple Stored XSS in Mailings
In CiviMail, multiple fields and screens could be used as vectors for cross-site scripting.
Exploiting this requires that the attacker have permission to manage CiviMail content.
CIVI-SA-2026-28: Escalation via Extension Download API
The Extension Download API provides administrators with tools for installing and sideloading extensions. The API is available in PHP, HTTP, CLI, etc. To execute the API, both the POSIX process and the CiviCRM user must have certain permissions.
The issue here is not a specific vulnerability in the API; on its own, it respects ordinary permissioning. However, if the system has another vulnerability (such as XSS), then the Extension Download API is an appealing target for escalation.
CIVI-SA-2026-27: Stored XSS in Participant Status
On the "Find Participants" search, the participant status field was not properly escaped.
CIVI-SA-2026-26: Unauthorized access to Files via APIv3
With multiple entry-points in APIv3, there was an ability to move arbitrary files from the server filesystem.
CIVI-SA-2026-25: Stored XSS in Tag Name
When viewing a contact or viewing the manage tags screen, the tag name and tag set names were not properly escaped.
CIVI-SA-2026-24: RCE via File API
In the File API, there was inscufficent validation of the uri field to prevent path transversal. This is a follow up to CIVI-SA-2026-01
CIVI-SA-2026-23: Stored XSS in Price Field label
The price field label was not properly escaped for select price fields.
