# OctoPrint Unverified Password Change via Access Control Settings

Advisory record · `GHSA-5626-pw9c-hmjr`

- **Identifiers:** `GHSA-5626-pw9c-hmjr` · `CVE-2024-23637` · `PYSEC-2024-29`
- **State:** Confirmed
- **Severity:** CVSS 4.2 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html) · [CWE-620](https://cwe.mitre.org/data/definitions/620.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md) · [CWE-620](https://agentprime.io/advisories/tag/cwe-620.md)
- **Published:** 31 Jan 2024
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

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

## Affected packages

- `octoprint` (PyPI): affected `<1.10.0rc1`; fixed in `1.10.0rc1`

## Machine-written summary

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

> OctoPrint versions before 1.10.0rc1 (up to and including 1.9.3) let an admin change the password of other admin accounts, including their own, without re-entering the current password. An attacker who has hijacked an admin account could use this to lock actual admins out of the instance. Upgrade to 1.10.0rc1 or later; the source's only suggested workaround is to carefully vet who holds admin access.

Written 5 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

- 4.2 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L`, from CNA (GitHub_M)

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

## Timeline

- 31 Oct 2026, 14:36 UTC: First seen by agentprime
- 31 Oct 2026, 14:36 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-5626-pw9c-hmjr)

## Sources

- [GitHub Advisory Database: GHSA-5626-pw9c-hmjr](https://github.com/advisories/GHSA-5626-pw9c-hmjr)
- [OSV: GHSA-5626-pw9c-hmjr](https://osv.dev/vulnerability/GHSA-5626-pw9c-hmjr)
- <https://github.com/OctoPrint/OctoPrint/security/advisories/GHSA-5626-pw9c-hmjr>
- <https://nvd.nist.gov/vuln/detail/CVE-2024-23637>
- <https://github.com/OctoPrint/OctoPrint/commit/1729d167b4ae4a5835bbc7211b92c6828b1c4125>
- <https://github.com/OctoPrint/OctoPrint>
- <https://github.com/OctoPrint/OctoPrint/releases/tag/1.10.0rc1>
- <https://github.com/pypa/advisory-database/tree/main/vulns/octoprint/PYSEC-2024-29.yaml>

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-5626-pw9c-hmjr>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-5626-pw9c-hmjr/>. Everything for agents: <https://agentprime.io/llms.txt>.