CVE-2024-49377
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 · uneditedOctoPrint provides a web interface for controlling consumer 3D printers. OctoPrint versions up until and including 1.10.2 contain reflected XSS vulnerabilities in the login dialog and the standalone application key confirmation dialog. An attacker who successfully talked a victim into clicking on a specially crafted login link, or a malicious app running on a victim's computer triggering the application key workflow with specially crafted parameters and then redirecting the victim to the related standalone confirmation dialog could use this to retrieve or modify sensitive configuration settings, interrupt prints or otherwise interact with the OctoPrint instance in a malicious way. The above mentioned specific vulnerabilities of the login dialog and the standalone application key confirmation dialog have been patched in the bugfix release 1.10.3 by individual escaping of the detected locations. A global change throughout all of OctoPrint's templating system with the upcoming 1.11.0 release will handle this further, switching to globally enforced automatic escaping and thus reducing the attack surface in general. The latter will also improve the security of third party plugins. During a transition period, third party plugins will be able to opt into the automatic escaping. With OctoPrint 1.13.0, automatic escaping will be switched over to be enforced even for third party plugins, unless they explicitly opt-out.
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 confidenceOctoPrint versions up to 1.10.2 contain reflected XSS vulnerabilities in the login dialog and standalone application key confirmation dialog. Attackers craft malicious links or trigger application key workflows with specially crafted parameters to inject scripts that can access/modify sensitive configuration, interrupt prints, or interact maliciously with the OctoPrint instance.
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< 1.10.3CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed OctoPrint versionAccess the OctoPrint web interface and navigate to Settings > About, or check the version via the API at /api/version, or inspect the bundled version.py file in the installation directoryAffected if The displayed version is lower than 1.10.3 (e.g., 1.10.2, 1.10.1, 1.10.0, or any 1.9.x release)
-
Verify application key feature accessibilityCheck if the Application Keys API endpoint is reachable at /api/plugin/appkeys or navigate to Settings > API to confirm application keys are enabledAffected if Application keys are enabled and the version is below 1.10.3, making the confirmation dialog vulnerable to reflected XSS
-
Inspect web server logs for suspicious request parametersReview OctoPrint's access logs (typically in the logs directory under octoprint.log) for requests to login or application key endpoints containing unusual script-related characters such as <script>, javascript:, or encoded variations in URL parametersAffected if Such malicious parameter patterns appear in logs, indicating potential exploitation attempts
-
Check for unauthorized configuration changesExamine Settings > Appearance > Manager and Settings > API > Application Keys for any unexpected modifications, new API keys, or unfamiliar plugin configurations that could have been added via XSSAffected if Unexpected API keys, modified settings, or unfamiliar plugins are present that were not intentionally created by the administrator
You are affected if your OctoPrint installation is any version below 1.10.3 and the application keys feature is accessible or the login dialog can be reached via crafted URLs.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.10.3
Upgrade to OctoPrint 1.10.3 or later which patches the reflected XSS via individual escaping of detected locations; the upcoming 1.11.0 release will implement globally enforced automatic escaping.
1.10.3
- 1. Back up your OctoPrint configuration and data
- 2. Access your OctoPrint server via SSH or terminal
- 3. Stop the OctoPrint service
- 4. Upgrade OctoPrint to version 1.10.3 or later using your installation method (e.g., pip install --upgrade OctoPrint, or via your package manager)
- 5. Restart the OctoPrint service
- 6. Verify the upgrade was successful by checking the version in the UI (OctoPrint > Settings > About)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49377 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-49377 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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