dbcve.org
Junos SpaceApplication · Juniper

CVE-2025-59978

CRITICAL · 9.0 CVSS v3.1 Published 2025-10-09
Fix available
A fix is available. Upgrade to 24.1 or later.
See remediation →
94/100
Remediation priority · Urgent
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
An Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Juniper Networks Junos Space allows an attacker to store script tags directly in web pages that, when viewed by another user, enable the attacker to execute commands with the target's administrative permissions. This issue affects all versions of Junos Space before 24.1R4.

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

A stored (persistent) cross-site scripting vulnerability in Juniper Networks Junos Space allows authenticated attackers to inject malicious script tags into web pages. These scripts persist and execute when other administrative users view the affected pages, potentially allowing the attacker to hijack administrative sessions and execute commands with the victim's privileges.

MitigationUpgrade to Junos Space version 24.1R4 or later. Until the upgrade is applied, restrict administrative access to trusted users only and monitor for suspicious administrative activity.

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
Junos SpaceApplication
Affected:< 24.1= 24.1

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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 Junos Space is deployed
    Check your environment for Juniper Junos Space installations. This is typically a network management appliance. Look for the web interface accessible on port 443 or the CLI access method specific to Junos Space.
    Affected if Junos Space is present in your environment
  2. Determine the installed Junos Space version
    Log into the Junos Space web interface as an administrator and navigate to the Administration > System > Platform or similar system information page. Alternatively, access the CLI and use 'show version' or 'show system information' commands if available for Junos Space.
    Affected if The version displayed is lower than 24.1R4 (including any version < 24.1 or exactly 24.1)
  3. Confirm the vulnerability affects this installation
    Compare your installed version against the affected range: versions < 24.1 and version = 24.1 are vulnerable. Versions 24.1R4 and later are not affected.
    Affected if Your version is 24.1, 24.1R1, 24.1R2, 24.1R3, or any version prior to 24.1

You are affected if Juniper Junos Space is running and the installed version is 24.1 or any version prior to 24.1R4.

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 24.1 or later
Fixed in 24.1
Interim mitigation

Upgrade to Junos Space version 24.1R4 or later. Until the upgrade is applied, restrict administrative access to trusted users only and monitor for suspicious administrative activity.

Recommended fix High confidence

24.1R4

  1. Review the Junos Space upgrade documentation at supportportal.juniper.net for complete upgrade procedures
  2. Ensure you have a complete backup of the Junos Space database and configuration
  3. Schedule a maintenance window as upgrades may require downtime
  4. Download Junos Space 24.1R4 or later from the Juniper support portal
  5. Follow the documented upgrade path for your current version to reach 24.1R4
  6. Verify the upgrade was successful and the vulnerability is resolved
Caveat Review Junos Space 24.1R4 release notes for any changes to features, compatibility, or migration requirements before upgrading

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

Fix this in Junos Space Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA5.0 h
33.0 hours of engineering $5,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 $9,216.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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