dbcve.org
ThinmanagerApplication · Rockwellautomation

CVE-2024-45826

HIGH · 8.8 CVSS v3.1 Published 2024-09-12
Fix available
A fix is available. Upgrade to 13.1.3 / 13.2.2 or later.
See remediation →
94/100
Remediation priority · Urgent
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
CVE-2024-45826 IMPACT Due to improper input validation, a path traversal and remote code execution vulnerability exists when the ThinManager® processes a crafted POST request. If exploited, a user can install an executable file.

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 · moderate confidence

This is a path traversal vulnerability with remote code execution capability in ThinManager ThinManager®. The vulnerability stems from improper input validation when processing crafted POST requests, allowing an attacker to write arbitrary files (executables) to the filesystem by manipulating file paths.

MitigationApply vendor patches when available. Until then, restrict network access to ThinManager interfaces, implement strict input validation and path sanitization on all file upload/path-handling operations, and deploy a WAF to detect path traversal patterns.

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
ThinmanagerApplication
Affected:>= 13.1.0, < 13.1.3>= 13.2.0, < 13.2.2

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
High
Availability
High

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

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. Identify if ThinManager is installed
    Check for ThinManager installation by looking for the ThinManager application in Program Files, or check Windows Services for 'ThinManager' or 'ThinManager Terminal Services' services.
    Affected if ThinManager software is present on the system
  2. Determine the installed ThinManager version
    Open ThinManager application and navigate to Help > About, or check the Windows installed programs list for the ThinManager version number.
    Affected if The version is 13.1.0 through 13.1.2 (inclusive) OR 13.2.0 through 13.2.1 (inclusive)
  3. Identify if ThinManager web or API service is enabled
    Check ThinManager configuration for web services, RemoteWinConfig, or any HTTP-based API endpoints. Look for web service ports (typically 80/443 or custom ports) configured in ThinManager.
    Affected if HTTP/HTTPS web services or RemoteWinConfig interface is enabled and accessible
  4. Check network exposure of ThinManager interfaces
    Review firewall rules and network configuration to determine if ThinManager ports (default HTTP port 80, HTTPS port 443, or configured custom ports) are exposed to untrusted networks.
    Affected if ThinManager web or management interfaces are reachable from outside the trusted network

If ThinManager is installed with a version between 13.1.0-13.1.2 or 13.2.0-13.2.1 AND the web/API service is enabled and network-accessible, the environment is likely affected by this path traversal vulnerability.

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 13.1.3 / 13.2.2 or later
Fixed in 13.1.313.2.2
Interim mitigation

Apply vendor patches when available. Until then, restrict network access to ThinManager interfaces, implement strict input validation and path sanitization on all file upload/path-handling operations, and deploy a WAF to detect path traversal patterns.

Recommended fix High confidence

ThinManager 13.2.2 (or 13.1.3 for the 13.1.x branch)

  1. 1. Back up the current ThinManager configuration and database before proceeding with the update.
  2. 2. Download ThinManager version 13.2.2 (recommended) or 13.1.3 from the Rockwell Automation website or authorized distribution channel.
  3. 3. Stop the ThinManager service to ensure a clean update process.
  4. 4. Install the ThinManager update version 13.2.2 (or 13.1.3) using the standard installation procedure.
  5. 5. Start the ThinManager service after installation completes.
  6. 6. Verify the installation was successful by checking the ThinManager version in the application.
  7. 7. Test ThinManager functionality in a non-production environment before deploying to production.

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

Fix this in Thinmanager Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45826 — 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-45826 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