What is the CVSS score of CVE-2026-32755?

CVE-2026-32755 has a CVSS 3.1 base score of 5.7 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N. EPSS exploitation probability: 0.0%.

Which versions of PHP are affected by CVE-2026-32755?

CVE-2026-32755 presents moderate security risk, a cross-site request forgery vulnerability rated CVSS 5.7. Users could be tricked into performing unintended actions.. A patch is available.

How to fix or mitigate CVE-2026-32755?

Within 30 days: Identify affected systems and apply vendor patches as part of regular patch cycle. Verify anti-CSRF tokens are enforced.

PHP CVE-2026-32755

MEDIUM

Cross-Site Request Forgery (CSRF) (CWE-352)

2026-03-16 https://github.com/Admidio/admidio

GHSA-h8gr-qwr6-m9gx

CSRF PHP

5.7

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

5.7 MEDIUM

AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Lifecycle Timeline

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

Analysis Generated

Mar 17, 2026 - 08:13 vuln.today

CVE Published

Mar 16, 2026 - 21:17 nvd

MEDIUM 5.7

DescriptionGitHub Advisory

Summary

The save_membership action in modules/profile/profile_function.php saves changes to a member's role membership start and end dates but does not validate the CSRF token. The handler checks stop_membership and remove_former_membership against the CSRF token but omits save_membership from that check. Because membership UUIDs appear in the HTML source visible to authenticated users, an attacker can embed a crafted POST form on any external page and trick a role leader into submitting it, silently altering membership dates for any member of roles the victim leads.

Details

CSRF Check Is Absent for save_membership

File: D:/bugcrowd/admidio/repo/modules/profile/profile_function.php, lines 40-42

The CSRF guard covers only two of the three mutative modes:

php

if (in_array($getMode, array('stop_membership', 'remove_former_membership'))) {
    // check the CSRF token of the form against the session token
    SecurityUtils::validateCsrfToken($_POST['adm_csrf_token']);
}

The save_membership mode is missing from this array. The handler then proceeds to read dates from $_POST and update the database without any token verification:

php

} elseif ($getMode === 'save_membership') {
    $postMembershipStart = admFuncVariableIsValid($_POST, 'adm_membership_start_date', 'date', array('requireValue' => true));
    $postMembershipEnd   = admFuncVariableIsValid($_POST, 'adm_membership_end_date',   'date', array('requireValue' => true));

    $member = new Membership($gDb);
    $member->readDataByUuid($getMemberUuid);
    $role = new Role($gDb, (int)$member->getValue('mem_rol_id'));

    // check if user has the right to edit this membership
    if (!$role->allowedToAssignMembers($gCurrentUser)) {
        throw new Exception('SYS_NO_RIGHTS');
    }
    // ... validates dates ...
    $role->setMembership($user->getValue('usr_id'), $postMembershipStart, $postMembershipEnd, ...);
    echo 'success';
}

File: D:/bugcrowd/admidio/repo/modules/profile/profile_function.php, lines 131-169

The Form Does Generate a CSRF Token (Not Validated)

File: D:/bugcrowd/admidio/repo/modules/profile/roles_functions.php, lines 218-241

The membership date form is created via FormPresenter, which automatically injects an adm_csrf_token hidden field into every form. However, the server-side save_membership handler never retrieves or validates this token. An attacker's forged form does not need to include the token at all, since the server does not check it.

Who Can Be Exploited as the CSRF Victim

File: D:/bugcrowd/admidio/repo/src/Roles/Entity/Role.php, lines 98-121

The allowedToAssignMembers() check grants write access to:

Any user who is isAdministratorRoles() (role administrators), or
Any user who is a leader of the target role when the role has rol_leader_rights set to ROLE_LEADER_MEMBERS_ASSIGN or ROLE_LEADER_MEMBERS_ASSIGN_EDIT

Role leaders are not system administrators. They are regular members who have been designated as group leaders (e.g., a sports team captain or committee chair). This represents a low-privilege attack surface.

UUIDs Are Discoverable from HTML Source

The save URL for the membership date form is embedded in the profile page HTML:

/adm_program/modules/profile/profile_function.php?mode=save_membership&user_uuid=<UUID>&member_uuid=<UUID>

Any authenticated member who can view a profile page can extract both UUIDs from the page source.

PoC

The attacker hosts the following HTML page and tricks a role leader into visiting it while logged in to Admidio:

html

<!DOCTYPE html>
<html>
<body onload="document.getElementById('csrf_form').submit()">
  <form id="csrf_form"
        method="POST"
        action="https://TARGET/adm_program/modules/profile/profile_function.php?mode=save_membership&user_uuid=<VICTIM_USER_UUID>&member_uuid=<MEMBERSHIP_UUID>">
    <input type="hidden" name="adm_membership_start_date" value="2000-01-01">
    <input type="hidden" name="adm_membership_end_date"   value="2000-01-02">
  </form>
</body>
</html>

Expected result: The target member's role membership dates are overwritten to 2000-01-01 through 2000-01-02, effectively terminating their active membership immediately (end date is in the past).

Note: No adm_csrf_token field is required because the server does not validate it for save_membership.

Impact

Unauthorized membership date manipulation: A role leader's session can be silently exploited to change start and end dates for any member of roles they lead. Setting the end date to a past date immediately terminates the member's active participation.
Effective access revocation: Membership in roles controls access to role-restricted features (events visible only to role members, document folders with upload rights, and mailing list memberships). Revoking membership via CSRF removes these access rights.
Covert escalation: An attacker could also extend a restricted membership period beyond its authorized end date, maintaining access for a user who should have been deactivated.
No administrative approval required: The impact occurs silently on the victim's session with no confirmation dialog or notification email.

Recommended Fix

Fix 1: Add `save_membership` to the existing CSRF validation check

php

// File: modules/profile/profile_function.php, lines 40-42
if (in_array($getMode, array('stop_membership', 'remove_former_membership', 'save_membership'))) {
    // check the CSRF token of the form against the session token
    SecurityUtils::validateCsrfToken($_POST['adm_csrf_token']);
}

Fix 2: Use the form-object validation pattern (consistent with other write endpoints)

php

} elseif ($getMode === 'save_membership') {
    // Validate CSRF via form object (consistent pattern used by DocumentsService, etc.)
    $membershipForm = $gCurrentSession->getFormObject($_POST['adm_csrf_token']);
    $formValues = $membershipForm->validate($_POST);

    $postMembershipStart = $formValues['adm_membership_start_date'];
    $postMembershipEnd   = $formValues['adm_membership_end_date'];
    // ... rest of save logic unchanged
}

AnalysisAI

Admidio's profile membership management function fails to validate CSRF tokens on the save_membership action, allowing an attacker to forge requests that modify membership start and end dates for any member of roles led by the victim. While other membership-related actions (stop_membership, remove_former_membership) include CSRF protection, save_membership was omitted from validation, enabling silent privilege escalation or access revocation through cross-site request forgery. A proof-of-concept exists demonstrating immediate exploitation by embedding a form on an external page.

Technical ContextAI

The vulnerability exists in Admidio (pkg:composer/admidio_admidio), a PHP-based group and event management platform, specifically in modules/profile/profile_function.php. The root cause is an incomplete CSRF token validation check (CWE-352: Cross-Site Request Forgery). While the codebase implements SecurityUtils::validateCsrfToken() for mutative operations, the save_membership mode was excluded from the if-statement array that triggers validation. The handler processes POST parameters (adm_membership_start_date, adm_membership_end_date) and updates the database via Role::setMembership() without confirming the request originated from an authenticated session form. The FormPresenter does generate and inject an adm_csrf_token hidden field into the membership form HTML, but this token is never retrieved or validated server-side for save_membership requests, making the client-side token generation ineffective.

RemediationAI

Upgrade Admidio to the patched version released by the vendor (refer to https://github.com/Admidio/Admidio/security/advisories/GHSA-h8gr-qwr6-m9gx for the exact version number). The primary fix is straightforward: add 'save_membership' to the CSRF validation check array in modules/profile/profile_function.php line 40, ensuring SecurityUtils::validateCsrfToken($_POST['adm_csrf_token']) is called before processing membership date changes. Until patching is possible, apply defense-in-depth controls: enforce SameSite=Strict cookie policy on the session cookie to mitigate cross-site request forgery, restrict profile_function.php access via IP allowlist if the Admidio instance is internal-only, and implement Content Security Policy headers to limit form submissions to same-origin destinations. Additionally, audit membership changes via database logs to detect silent modifications and configure email notifications for role leaders on membership updates.