A stored cross-site scripting (XSS) vulnerability exists in the Admidio web interface. It allows a role administrator (a lower privilege than full administrator) to inject a malicious role name that executes JavaScript in the session of any user who views a profile page containing that role's membership — including full administrators .
The vulnerability is compounded by an input length restriction bypass (external script loading) and results in full privilege escalation : the attacker can steal the victim's CSRF token and assign the Administrator role to their own account, achieving complete account takeover.
Severity (CVSS 3.1): P2 / High — AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N (≈ 8.0)
Stored XSS via role name in data-message attribute (profile view)
File: modules/profile/roles_functions.php , line ~209
Context: Membership delete link rendered on a user profile page
Related presenter: src/UI/Presenter/GroupsRolesPresenter.php (role edit form, rol_name field, maxLength 100)
The delete-membership link is built by PHP string concatenation (not Smarty), and inserts the role name in raw form:
'database' format returns the value without the HTML-encoding that Entity::getValue() applies for text/varchar columns. The role name is therefore emitted verbatim into the double-quoted attribute. A role name containing a double quote breaks out of the attribute and injects arbitrary HTML/JavaScript.
The role name itself is collected through a text -type form field, which is only passed through StringUtils::strStripTags() (removes tags, keeps quotes), so quotes survive into the database.
A user with permissions "Organize and assign roles" or user with role-administrator can put xss payload to Role name
Create a role whose name contains an XSS payload, e.g.:
Assign that role to any user (or have a user self-register into it).
When a full administrator (or any user with delete-membership rights) opens that user's profile page and the membership delete link is rendered, the payload executes in the viewer's session.
This is a privilege escalation : role administrator → full administrator session compromise.
Step 1: Create the malicious role
Log in as a role administrator.
Go to Groups & Roles → create a new role.
Set the role Name to:
Step 2: Host the external payload
Create x.js on the attacker's server (port 6767):
Step 3: Trigger the XSS
Assign the malicious role to a target user (or wait for a user to join).
Log in as a full administrator .
Open the target user's Profile page. (or Groups & roles )
Hover over the delete-membership icon for the malicious role.
Step 4: Verify the exfiltration
The attacker's server (port 6969) receives:
Step 5: Verify privilege escalation
Log in with the attacker's account.
Navigate to Profile → confirm "Administrator" role is listed.
Access Preferences or Organizations (admin-only pages) → access granted.
Full chain: XSS → CSRF token theft → Privileged action execution → Account takeover
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
