# SimpleSAMLphp exposes credentials in session storage

Advisory record · `GHSA-7wh8-jrq7-p27f`

- **Identifiers:** `GHSA-7wh8-jrq7-p27f` · `PKSA-ytw1-2sfw-nwys`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-522](https://cwe.mitre.org/data/definitions/522.html)
- **Tags:** [Hard-coded credentials](https://agentprime.io/advisories/tag/hard-coded-credentials.md)
- **Published:** 28 May 2024
- **Updated:** 3 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 28 May 2024, 18:28 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `simplesamlphp/simplesamlphp` (Packagist): affected `>=1.16.0, <1.16.3`; fixed in `1.16.3`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> SimpleSAMLphp versions 1.16.0 up to but not including 1.16.3 store user credentials in the session when the SAML ECP profile is disabled on an Identity Provider that has metadata for ECP-capable entities. An attacker with access to the session store or its backups, such as an administrator or someone with access to those systems, could read the stored usernames and passwords. Upgrade to SimpleSAMLphp 1.16.3.

Written 4 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 14:28 UTC: First seen by agentprime
- 31 Oct 2026, 14:28 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-7wh8-jrq7-p27f)

## Sources

- [GitHub Advisory Database: GHSA-7wh8-jrq7-p27f](https://github.com/advisories/GHSA-7wh8-jrq7-p27f)
- [OSV: GHSA-7wh8-jrq7-p27f](https://osv.dev/vulnerability/GHSA-7wh8-jrq7-p27f)
- <https://github.com/simplesamlphp/simplesamlphp/commit/44d1e3052930d93f0f554c25bc7c7602f8136880>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/simplesamlphp/simplesamlphp/2018-12-20.yaml>
- <https://github.com/simplesamlphp/simplesamlphp>
- <https://simplesamlphp.org/security/201812-01>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-7wh8-jrq7-p27f>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-7wh8-jrq7-p27f/>. Everything for agents: <https://agentprime.io/llms.txt>.
