Admidio authorization bypass in bulk profile editing
Affects Admidio 5.0.0 through 5.0.17 where non-administrative Group Leaders can edit role members and restricted profile fields are in use. Fixed in 5.0.18.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.0.18
- Who is exposed
- Specific setups only
Summary
Admidio, a web-based membership management application, has an authorization flaw in its profile editing module that lets logged-in group leaders get around field-level restrictions. Remotely, an attacker with low-privilege login can read restricted profile field values and change restricted fields in other members' profiles.
Written by a model
Original description
Admidio 5.0.0 before 5.0.18 contains an improper authorization vulnerability in modules/profile/profile_new.php that allows authenticated Group Leaders to bypass field-level profile restrictions. Attackers can request mode=html_selection to read restricted field values and submit mode=save requests to modify restricted member profile fields.
Who should check
Teams running Admidio 5.0.0 through 5.0.17 where Group Leaders can edit members of a role, especially on Apache with PHP and MariaDB as tested.
“Admidio 5.0.0 before 5.0.18 contains an improper authorization vulnerability”
What to do
Check whether your setup matches what the bug needs.
Admidio versions 5.0.0 through 5.0.17 (fixed in 5.0.18) The attacker is a non-administrative Group Leader with permission to edit members of a role, and the restricted profile fields are set up so the leader cannot see them normallyUpgrade 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-134260 (Admidio 5.0.0 before 5.0.18 Authorization Bypass via Bulk Profile Edit in profile_new.php), 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-134260 (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 versions 5.0.0 through 5.0.17 (fixed in 5.0.18) (source: https://www.vulncheck.com/advisories/admidio-5.0.0-before-5.0.18-authorization-bypass-via-bulk-profile-edit-in-profile-new-php)
- The attacker is a non-administrative Group Leader with permission to edit members of a role, and the restricted profile fields are set up so the leader cannot see them normally (source: https://github.com/Admidio/admidio/security/advisories/GHSA-mhjp-mpjr-7rx5)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134260 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134260 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-mhjp-mpjr-7rx5
- https://www.vulncheck.com/advisories/admidio-5.0.0-before-5.0.18-authorization-bypass-via-bulk-profile-edit-in-profile-new-php
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-134260
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-134260"}.Affected versions
- Admidio admidioFrom 5.0.0 · fixed in 5.0.18
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 20 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · Admidio/admidio · Advisory GHSA-mhjp-mpjr-7rx5 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134260 |
| Record | NVD · CVE-2026-134260 |
| Other links 1 | |
| Link | vulncheck.com · advisories/admidio-5.0.0-before-5.0.18-authorization-bypass-via-bulk-profile-edit-in-profile-new-php |
Questions about CVE-2026-134260
Is CVE-2026-134260 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 Group Leader with permission to edit a role's members can read and change restricted profile fields, such as personal identification numbers or private contact details, that the leader should not be able to access.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-134260?
admidio: from 5.0.0 before 5.0.18.
Source: cve.now feed data
Am I affected, and how do I check?
Admidio versions 5.0.0 through 5.0.17 are affected, in setups where restricted profile fields are configured and Group Leaders have permission to edit members of a role. Compare the installed Admidio version against that range.
Source: vulncheck.com, github.com
How do I fix CVE-2026-134260?
Upgrade to Admidio 5.0.18, the fixed version.
Source: vulncheck.com, github.com
Related
- CVE-2026-134258Admidio 5.0.0 before 5.0.18 Path Traversal to Stored XSS via File Rename
- CVE-2026-134262Admidio 5.0.0 before 5.0.18 Stored XSS via Role Name in Profile View
- CVE-2026-82657Admidio before 5.0.12 Authentication Bypass via RSS feeds
- CVE-2026-109329Admidio 4.3.2 through 4.3.17 and 5.0.0 before 5.0.15 Cross-Organization Access Control Bypass via members_assignment.php
- CVE-2026-134254Admidio 5.0.0 before 5.0.18 Path Traversal via Documents & Files Rename
- CVE-2026-134261Admidio 5.0.17 IDOR in mylist.php Exposes Private List Configurations
No corrections so far. Something wrong on this page? Report an error.