PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-69092 Admidio CVE debrief

CVE-2026-69092 is a reflected cross-site scripting vulnerability affecting Admidio versions before 5.0.11. The vulnerability is located in the SSO/SAML endpoint and allows unauthenticated attackers to inject arbitrary JavaScript through SAML Issuer elements or LightSaml library parameters. This can lead to code execution in users' browsers and session hijacking.

Vendor
Admidio
Product
Unknown
CVSS
MEDIUM 6.9
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-03
Original CVE updated
2026-09-09
Advisory published
2026-08-03
Advisory updated
2026-09-09

Who should care

Defenders responsible for Admidio instances, security teams, and administrators should be aware of this vulnerability and take necessary actions to prevent exploitation. This includes verifying Admidio versions, applying patches, reviewing and restricting input to SAML Issuer elements and LightSaml library parameters, and monitoring for suspicious activity on Admidio instances.

Why it matters

CVE-2026-69092 is a reflected cross-site scripting vulnerability in Admidio versions before 5.0.11. Defenders should prioritize verifying Admidio versions and applying patches to prevent exploitation. Security teams and administrators responsible for Admidio instances should be aware of this vulnerability and take necessary actions.

  • Code execution in users' browsers
  • Session hijacking by unauthenticated attackers
  • Potential for arbitrary JavaScript injection

Technical summary

The vulnerability is caused by the SSO/SAML endpoint echoing unencoded exception messages to the HTTP response in Admidio versions before 5.0.11. This allows unauthenticated attackers to inject arbitrary JavaScript through SAML Issuer elements or LightSaml library parameters, leading to code execution in users' browsers and session hijacking. Defenders should prioritize verifying Admidio versions and applying patches to prevent exploitation. Security teams and administrators responsible for Admidio instances should be aware of this vulnerability and take necessary actions.

Defensive priority

Defenders should prioritize verifying Admidio versions and applying patches to prevent exploitation.

Recommended defensive actions

  • Verify Admidio version and apply patch to 5.0.11 or later
  • Review and restrict input to SAML Issuer elements and LightSaml library parameters
  • Monitor for suspicious activity on Admidio instances
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details about the vulnerability in Admidio versions before 5.0.11. Additional information from the vendor and other sources may be necessary to fully understand the issue, including verifying Admidio versions, reviewing and restricting input to SAML Issuer elements and LightSaml library parameters, and monitoring for suspicious activity. Defenders should prioritize verifying Admidio versions and applying patches to prevent exploitation.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-69092 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-69092

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-69092 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-69092

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

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.