Skip to main content
Menu
CVEs

Admidio remote code injection in role names

Only affects Admidio 5.0.0 before 5.0.18 where a role name is rendered unencoded in the profile view. Fixed in 5.0.18.

CVE-2026-134262Published November 21, 2026, updated

9.2CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 5.0.18
Who is exposed
Specific setups only

Summary

Written by a model

Admidio 5.0.0 before 5.0.18 contains a stored cross-site scripting vulnerability that allows role administrators to inject JavaScript by placing quote-breaking payloads in role names rendered unencoded in the data-message attribute in modules/profile/roles_functions.php. Attackers can execute scripts when a full administrator views an affected profile page, stealing the CSRF token to assign themselves the Administrator role.

Who should check

Teams running Admidio 5.0.0 through 5.0.17 where role administrators manage roles and full administrators view user profiles

“Affecting admidio >= 5.0.0, < 5.0.18”

vulncheck.com

What to do

  1. Check whether your setup matches what the bug needs.

    Admidio 5.0.0 before 5.0.18 Role name is rendered unencoded in the data-message attribute Victim is a full administrator or a user with delete-membership rights who opens a profile page showing the malicious role
  2. Upgrade to a fixed version: 5.0.18.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134262 (Admidio 5.0.0 before 5.0.18 Stored XSS via Role Name in Profile View), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134262 (entry last updated 2026-11-21):
Affected:
- Admidio admidio: from 5.0.0, fixed in 5.0.18
Fixed versions: 5.0.18.
Conditions (all must be true for the bug to be hit):
- Admidio 5.0.0 before 5.0.18 (source: https://www.vulncheck.com/advisories/admidio-5.0.0-before-5.0.18-stored-xss-via-role-name-in-profile-view)
- Role name is rendered unencoded in the data-message attribute (source: https://www.vulncheck.com/advisories/admidio-5.0.0-before-5.0.18-stored-xss-via-role-name-in-profile-view)
- Victim is a full administrator or a user with delete-membership rights who opens a profile page showing the malicious role (source: https://github.com/Admidio/admidio/security/advisories/GHSA-v28h-h5qh-45hr)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, a user action.
CISA KEV: CVE-2026-134262 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134262 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Admidio/admidio/security/advisories/GHSA-v28h-h5qh-45hr
- https://www.vulncheck.com/advisories/admidio-5.0.0-before-5.0.18-stored-xss-via-role-name-in-profile-view
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134262
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134262"}.

Affected versions

cve.now Index

17Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.2/10CVSS 9.2
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 24 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · Admidio/admidio · Advisory GHSA-v28h-h5qh-45hr
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134262
RecordNVD · CVE-2026-134262
Other links 1
Linkvulncheck.com · advisories/admidio-5.0.0-before-5.0.18-stored-xss-via-role-name-in-profile-view

Questions about CVE-2026-134262

Is CVE-2026-134262 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A malicious role name is rendered unencoded in the data-message attribute of a profile page, so script placed in the role name runs in the browser of an administrator or member with delete-membership rights who opens that profile. The injected script can steal the victim's CSRF token and assign the Administrator role to the attacker's own account.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134262?

admidio: from 5.0.0 before 5.0.18.

Source: cve.now feed data

Am I affected, and how do I check?

Admidio 5.0.0 before 5.0.18 is affected. To check your version, look at the version shown in the Admidio installation or its release files; a version of 5.0.18 or later is not in the affected range. Exposure also depends on a role name that renders unencoded and on viewers who hold full administrator or delete-membership rights.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134262?

Upgrade Admidio to version 5.0.18 or later, which is the fixed version.

Source: vulncheck.com, github.com

No corrections so far. Something wrong on this page? Report an error.