dbcve.org
Octopus ServerApplication · Octopus

CVE-2025-0513

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-11
Fix available
A fix is available. Upgrade to 2024.3.12985 / 2024.4.6962 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
In affected versions of Octopus Server error messages were handled unsafely on the error page. If an adversary could control any part of the error message they could embed code which may impact the user viewing the error message.

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

Octopus Server contains a reflected Cross-Site Scripting (XSS) vulnerability in its error page handling. User-controlled error message content is rendered unsafely without proper sanitization or encoding, allowing an attacker to inject malicious script that executes in the context of a victim's browser when viewing error pages.

MitigationImplement context-appropriate output encoding for all error message content before rendering on the error page. Alternatively, deploy the vendor patch when available.

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
Octopus ServerApplication
Affected:>= 2024.3.164, < 2024.3.12985>= 2024.4.401, < 2024.4.6962

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Identify Octopus Server version
    Locate the installed Octopus Server version via the web interface (Help > About), REST API endpoint /api/about, or server logs
    Affected if The installed version falls within 2024.3.164 to 2024.3.12985, or 2024.4.401 to 2024.4.6962
  2. Compare version to affected ranges
    Compare your installed version number against the affected ranges: >= 2024.3.164 and < 2024.3.12985, or >= 2024.4.401 and < 2024.4.6962
    Affected if Your version is greater than or equal to 2024.3.164 but less than 2024.3.12985, OR greater than or equal to 2024.4.401 but less than 2024.4.6962
  3. Verify web interface accessibility
    Confirm the Octopus Server web interface is accessible to users or attackers who could trigger error conditions
    Affected if The web interface is exposed and users can trigger error conditions that display error pages
  4. Identify custom error handling
    Review any custom error handlers, error message templates, or integrations that pass user-supplied input into error page content
    Affected if Custom error handlers or integrations pass user-controlled content into error page rendering without sanitization
  5. Audit error logging configuration
    Check if error responses can include unsanitized user input in the error message field (for example, via query parameters or form submissions that trigger errors)
    Affected if User-supplied input can be reflected in error page messages without proper encoding

You are affected if your Octopus Server version is within the specified vulnerable ranges AND your web interface can display error pages containing user-controlled content.

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 2024.3.12985 / 2024.4.6962 or later
Fixed in 2024.3.129852024.4.6962
Interim mitigation

Implement context-appropriate output encoding for all error message content before rendering on the error page. Alternatively, deploy the vendor patch when available.

Recommended fix High confidence

Upgrade to Octopus Server 2024.3.12985 (for 2024.3.x users) or 2024.4.6962 (for 2024.4.x users), or any later stable release in the respective branch

  1. Identify the current Octopus Server version by navigating to Configuration > Nodes in the Octopus Web Portal, or by running `octopus --version` from the server CLI
  2. Determine which release branch is in use (2024.3.x or 2024.4.x) to select the appropriate upgrade path
  3. Download the fixed version: 2024.3.12985 for the 2024.3 branch, or 2024.4.6962 for the 2024.4 branch (or a later stable release in the same branch)
  4. Follow standard Octopus Server upgrade procedures: back up the database, stop the Octopus service, run the installer for the new version, and verify the upgrade completes successfully
  5. After upgrade, confirm the version matches the expected fixed release in Configuration > Nodes
  6. Test that error pages render without executing any injected scripts to verify the XSS fix is working

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

Fix this in Octopus Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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