# Insufficient token expiration in Serenity

Advisory record · `GHSA-2hp9-3xfr-r9w2`

- **Identifiers:** `GHSA-2hp9-3xfr-r9w2` · `CVE-2023-31287`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-640](https://cwe.mitre.org/data/definitions/640.html)
- **Tags:** [CWE-640](https://agentprime.io/advisories/tag/cwe-640.md)
- **Published:** 27 Apr 2023
- **Updated:** 31 Jan 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 27 Apr 2023, 03:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `Serenity.Net.Core` (NuGet): affected `<6.7.0`; fixed in `6.7.0`
- `Serenity.Net.Web` (NuGet): affected `<6.7.0`; fixed in `6.7.0`

## 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

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.0043, the 38th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:22 UTC: First seen by agentprime
- 31 Oct 2026, 15:22 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-2hp9-3xfr-r9w2)

## Sources

- [GitHub Advisory Database: GHSA-2hp9-3xfr-r9w2](https://github.com/advisories/GHSA-2hp9-3xfr-r9w2)
- [OSV: GHSA-2hp9-3xfr-r9w2](https://osv.dev/vulnerability/GHSA-2hp9-3xfr-r9w2)
- <https://nvd.nist.gov/vuln/detail/CVE-2023-31287>
- <https://github.com/serenity-is/Serenity/commit/11b9d267f840513d04b4f4d4876de7823a6e48d2>
- <https://github.com/serenity-is/Serenity>
- <https://packetstorm.news/files/id/172648>
- <http://packetstormsecurity.com/files/172648/Serenity-StartSharp-Software-File-Upload-XSS-User-Enumeration-Reusable-Tokens.html>
- <http://seclists.org/fulldisclosure/2023/May/14>

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-2hp9-3xfr-r9w2>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-2hp9-3xfr-r9w2/>. Everything for agents: <https://agentprime.io/llms.txt>.