# CVE-2013-10077: OctoPrint API Key settings.py getSettings information disclosure


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-8x4f-fx35-j5j9

## What is CVE-2013-10077?

CVE-2013-10077 is a medium-severity vulnerability in OctoPrint, published on 26 Oct 2026. 

### Official description

A weakness has been identified in OctoPrint 1.0.0. This impacts the function getSettings of the file src/octoprint/server/ajax/settings.py of the component API Key Handler. This manipulation causes information disclosure. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be used for attacks. Upgrading to version 1.1.0-rc1 will fix this issue. Patch name: eccc9d6fbde0c46cdd6e255fd5ce9a30077ba954. You should upgrade the affected component. Affected is a 2013 release where access control was not yet implemented and the endpoint was part of first-run setup). The API key has been admin-gated since 1.2.0 and GET /api/settings is protected by Permissions.SETTINGS_READ plus reauthentication in all current releases.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2013-10077?


## How do I fix CVE-2013-10077?

No fix has been published for CVE-2013-10077 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-10077 being exploited?

There is no known exploitation of CVE-2013-10077 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-10077 and fix it if it is affected.

What it is: CVE-2013-10077 is a medium-severity vulnerability in OctoPrint, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2013-10077 in the wild and no public exploit code.

Affected product: OctoPrint. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-10077/ (Markdown: https://insights.sbomify.com/CVE-2013-10077/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-10077
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-10077
- OSV: https://osv.dev/vulnerability/CVE-2013-10077

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-10077/
Summaries are generated and may contain mistakes; the official description above is the record.