dbcve.org
Junos SpaceApplication · Juniper

CVE-2025-59991

MEDIUM · 6.1 CVSS v3.1 Published 2025-10-09
Fix available
A fix is available. Upgrade to 24.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 inject script tags in the Device Management pages that, when visited by another user, enable the attacker to execute commands with the target's permissions, including an administrator. 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 · moderate confidence

A stored XSS vulnerability exists in Junos Space's Device Management pages where script tags can be injected into user-controlled fields. When other users visit the affected pages, the injected JavaScript executes within their browser context, allowing the attacker to perform actions with the victim's permissions, including administrative commands.

MitigationUpgrade Junos Space to version 24.1R4 or later to remediate this vulnerability.

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
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 checks

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

  1. Identify Junos Space version
    Log into the Junos Space web UI and navigate to Administration > System > Software or use the CLI command 'show version' on the Space device
    Affected if The installed version is lower than 24.1 or exactly 24.1
  2. Confirm Device Management access
    Navigate to the Device Management section in the Junos Space UI (Devices > Device Management or similar path)
    Affected if User-controlled fields such as device names, hostnames, IP addresses, or description fields are visible and editable
  3. Check for user-controlled fields in Device Management
    Examine Device Management pages for editable fields where users can input custom values - look for fields like device alias, hostname, description, or custom attributes
    Affected if These fields accept user input without proper sanitization (the vulnerable condition)
  4. Verify browser context execution risk
    Review whether multiple user roles have access to the same Device Management pages - the XSS affects other users viewing the injected content
    Affected if Multiple users or roles can view the same device records

If Junos Space version is < 24.1 or = 24.1 AND the Device Management pages with user-controlled fields are accessible to users, the environment is vulnerable to stored XSS via script injection.

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 Junos Space to version 24.1R4 or later to remediate this vulnerability.

Recommended fix High confidence

24.1R4 or later

  1. 1. Backup the Junos Space configuration and any critical data before proceeding with the upgrade.
  2. 2. Download Junos Space 24.1R4 (or a later stable release) from the Juniper Networks support portal at supportportal.juniper.net.
  3. 3. Access the Junos Space web interface with administrator privileges.
  4. 4. Navigate to the Administration > System > Software Update section.
  5. 5. Upload the 24.1R4 software image to Junos Space.
  6. 6. Follow the on-screen prompts to install the software update.
  7. 7. After installation, verify the system is running version 24.1R4 or later.
  8. 8. Test the Device Management pages to confirm the XSS vulnerability is remediated.
Caveat Standard Junos Space upgrade precautions apply - ensure backups are complete and plan for brief downtime

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

Fix this in Junos Space Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
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,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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