Skip to main content
Menu
CVEs

Admidio private list configuration read via IDOR in mylist.php

Affects Admidio 5.0.17 and current master (6.0.0-Beta1) for signed-in users with Lists module access who know another user's list UUID. Fixed in 5.0.18.

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

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 5.0.18
Who is exposed
Specific setups only

Summary

Admidio contains an insecure direct object reference flaw in its mylist.php page. Remotely, over the network, a logged-in user with Lists module access who knows another user's list UUID can read that private list's name, selected profile fields, sort order, and filter conditions.

Written by a model

Original description

Admidio before 5.0.18 contains an insecure direct object reference vulnerability in mylist.php that loads list configurations by the list_uuid parameter while checking only the organization, not the owner or private flag. Authenticated users with Lists module access who know a victim's list UUID can read its name, selected profile fields, sort order and filter conditions.

Who should check

Teams running Admidio 5.0.17 or 6.0.0-Beta1 where members can access the Lists module, such as organizations with private list configurations.

“it affects the supported v5.0.17 release and current master (6.0.0-Beta1)”

github.com

What to do

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

    Admidio 5.0.17 or 6.0.0-Beta1 (advisory says before 5.0.18) Attacker has Lists module access as a signed-in user Attacker must know the victim's list UUID Victim's list is private (not visible to all users) and stored under the victim's account
  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-134261 (Admidio 5.0.17 IDOR in mylist.php Exposes Private List Configurations), 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-134261 (entry last updated 2026-11-21):
Affected:
- Admidio admidio: from 5.0.17, fixed in 5.0.18
Fixed versions: 5.0.18.
Conditions (all must be true for the bug to be hit):
- Admidio 5.0.17 or 6.0.0-Beta1 (advisory says before 5.0.18) (source: https://github.com/Admidio/admidio/security/advisories/GHSA-w3q2-8f3p-c2mw)
- Attacker has Lists module access as a signed-in user (source: https://www.vulncheck.com/advisories/admidio-5.0.17-idor-in-mylist-php-exposes-private-list-configurations)
- Attacker must know the victim's list UUID (source: https://github.com/Admidio/admidio/security/advisories/GHSA-w3q2-8f3p-c2mw)
- Victim's list is private (not visible to all users) and stored under the victim's account (source: https://github.com/Admidio/admidio/security/advisories/GHSA-w3q2-8f3p-c2mw)
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-134261 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134261 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-w3q2-8f3p-c2mw
- https://www.vulncheck.com/advisories/admidio-5.0.17-idor-in-mylist-php-exposes-private-list-configurations
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-134261
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-134261"}.

Affected versions

cve.now Index

15Pof 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
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 22 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · Admidio/admidio · Advisory GHSA-w3q2-8f3p-c2mw
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134261
RecordNVD · CVE-2026-134261
Other links 1
Linkvulncheck.com · advisories/admidio-5.0.17-idor-in-mylist-php-exposes-private-list-configurations

Questions about CVE-2026-134261

Is CVE-2026-134261 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?

Signed-in users with Lists module access can read other users' private list configurations, including the list name, selected profile fields, sort order and filter conditions. The list cannot be modified or deleted through this path.

Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-134261?

admidio: from 5.0.17 before 5.0.18.

Source: cve.now feed data

Am I affected, and how do I check?

Admidio 5.0.17 and current master (6.0.0-Beta1) are affected, according to the advisory's statement that it affects versions before 5.0.18. The exposure requires a private list stored under another user's account, and the requester must know that list's non-enumerable UUID.

Source: github.com, vulncheck.com

How do I fix CVE-2026-134261?

Upgrade to Admidio 5.0.18 or later, which the product data lists as the fixed version.

Source: github.com, vulncheck.com

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