dbcve.org
OctoprintApplication

CVE-2024-51493

MEDIUM · 6.5 CVSS v3.1 Published 2024-11-05
Fix available
A fix is available. Upgrade to 1.10.3 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
OctoPrint provides a web interface for controlling consumer 3D printers. OctoPrint versions up until and including 1.10.2 contain a vulnerability that allows an attacker that has gained temporary control over an authenticated victim's OctoPrint browser session to retrieve/recreate/delete the user's or - if the victim has admin permissions - the global API key without having to reauthenticate by re-entering the user account's password. An attacker could use a stolen API key to access OctoPrint through its API, or disrupt workflows depending on the API key they deleted. This vulnerability will be patched in version 1.10.3 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OctoPrint versions up to 1.10.2 contain a vulnerability where an attacker with temporary control of an authenticated user's browser session can retrieve, recreate, or delete that user's API key (or global API key if admin) without requiring password re-authentication. This enables API access disruption or unauthorized API usage.

MitigationUpgrade OctoPrint to version 1.10.3 or later. There are no workarounds; the upgrade is the only mitigation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OctoprintApplication
Affected:< 1.10.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed OctoPrint version
    Access the web interface, click the OctoPrint logo (top left), or navigate to Settings > About. Alternatively, check the pip package version with: pip show octoprint | grep Version
    Affected if Version is displayed as less than 1.10.3 (e.g., 1.10.2, 1.10.1, 1.10.0, or any 1.x version below 1.10.3)
  2. Verify API key access through user settings
    Log into the OctoPrint web interface as any user, navigate to Settings > API. Observe whether the API key is visible and whether options to Regenerate or Delete the key are present without requiring password re-authentication.
    Affected if The API key is shown or the regenerate/delete buttons are functional without prompting for the user's password again after session login
  3. Check for admin user API key exposure
    Log in as an administrator user, navigate to Settings > API. Verify whether the global API key is accessible and whether it can be retrieved, regenerated, or deleted without re-entering credentials.
    Affected if The global API key operations (view/regenerate/delete) function without password re-authentication prompt

A user is affected if their installed OctoPrint version is below 1.10.3 AND they can access/modify API keys through the web interface without being prompted for password re-authentication after logging in.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.10.3 or later
Fixed in 1.10.3
Interim mitigation

Upgrade OctoPrint to version 1.10.3 or later. There are no workarounds; the upgrade is the only mitigation.

Recommended fix High confidence

1.10.3

  1. Backup your OctoPrint installation and configuration data before upgrading
  2. Upgrade OctoPrint to version 1.10.3 or later by following the standard upgrade procedure for your installation method
  3. After upgrading, verify the installation was successful by accessing the OctoPrint web interface
  4. If you suspect the vulnerability may have been exploited, consider rotating all API keys and reviewing access logs for suspicious activity

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Octoprint Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-51493 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-51493 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data