PatchSiren cyber security CVE debrief
CVE-2026-47228 Admidio CVE debrief
CVE-2026-47228 is a vulnerability in Admidio's user management solution. The `modules/registration.php` file has a mode `send_login` that regenerates a random password for a user and emails it in cleartext without validating a CSRF token. This allows an attacker to reset a user's password if the request is issued as a top-level navigation by a registration-administrator. The issue was fixed in version 5.0.10.
- Vendor
- Admidio
- Product
- Unknown
- CVSS
- MEDIUM 5.2
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-12
- Original CVE updated
- 2026-09-09
- Advisory published
- 2026-08-12
- Advisory updated
- 2026-09-09
Who should care
Defenders responsible for Admidio user management solution deployments should assess exposure and apply the patch to prevent potential password reset attacks. They should review user management configurations, ensure secure password reset processes, and monitor for potential exploitation attempts. Security teams and vulnerability management teams should prioritize verifying exposure and applying the patch.
Why it matters
CVE-2026-47228 allows an attacker to reset a user's password without validation, impacting Admidio user management solution deployments. Defenders should verify exposure and apply the patch.
- Password reset without interaction
- Potential unauthorized access to user accounts
- Need to verify exposure and apply patch
Technical summary
The `modules/registration.php` file in Admidio has a mode `send_login` that regenerates a random password for a user and emails it in cleartext without validating a CSRF token. This allows an attacker to reset a user's password if the request is issued as a top-level navigation by a registration-administrator. The issue arises from the lack of CSRF token validation in the `send_login` branch, unlike other state-changing modes in the same file. The vulnerability impacts Admidio user management solution deployments, allowing potential unauthorized access to user accounts.
Defensive priority
Defenders should prioritize verifying exposure and applying the patch, as the vulnerability allows password reset without interaction.
Recommended defensive actions
- Verify if Admidio version is prior to 5.0.10 and apply the patch if necessary
- Review user management configurations and ensure secure password reset processes
- Monitor for potential exploitation attempts
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, its impact, and the fix in version 5.0.10. Defenders should verify exposure by checking Admidio versions and configurations, and apply the patch if necessary. Evidence is limited to public sources and may not cover all affected deployments or variations. Further verification tasks are recommended.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-47228 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-47228
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-47228 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-47228
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/Admidio/admidio/security/advisories/GHSA-mx25-j3rc-6w2w
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.