dbcve.org
Junos SpaceApplication · Juniper

CVE-2025-59982

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 dashboard search field that, when visited by another user, enables 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 · high confidence

A stored Cross-site Scripting (XSS) vulnerability exists in Junos Space's dashboard search field. The application fails to properly sanitize input, allowing an attacker to inject malicious script tags. When other users access the dashboard, the embedded scripts execute with the victims' session privileges, enabling command execution including administrative actions.

MitigationUpgrade Junos Space to version 24.1R4 or later to obtain the vendor patch. Until then, restrict dashboard access and monitor for suspicious script injections in the search field.

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. Determine installed Junos Space version
    Log into the Junos Space web UI and navigate to Administration > System > System Information, or use the CLI command 'show version' on the Junos Space appliance to retrieve the software version number
    Affected if The displayed version is lower than 24.1 or exactly 24.1 (versions prior to 24.1R4 are vulnerable)
  2. Verify dashboard access is enabled
    Log into Junos Space and navigate to the main dashboard view. Confirm the dashboard search field is visible and accessible to your user account
    Affected if The dashboard search field is present and accessible to users
  3. Inspect for existing XSS payloads in search field
    View the dashboard page source using browser developer tools (F12), or examine any logged data for the dashboard search function to see if malicious script tags have been stored
    Affected if Script tags such as <script> or event handlers like onload/onerror appear in the dashboard search data or page source

You are affected if your Junos Space version is 24.1 or any version prior to 24.1R4 and the dashboard with its search field is accessible to users.

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 obtain the vendor patch. Until then, restrict dashboard access and monitor for suspicious script injections in the search field.

Recommended fix High confidence

24.1R4 (or any version after 24.1R4)

  1. 1. Identify the current Junos Space version by navigating to Administration > Junos Space > Junos Space Settings > Platform Settings in the web UI
  2. 2. Create a full backup of the Junos Space configuration and take a snapshot of the virtual machine if applicable
  3. 3. Review the Junos Space upgrade guide and release notes for 24.1R4 for any pre-upgrade requirements
  4. 4. Schedule a maintenance window as upgrades require downtime
  5. 5. Download Junos Space 24.1R4 or later from the Juniper support portal
  6. 6. Upload the upgrade package through the Junos Space web UI (Administration > Junos Space > Platform Settings > Firmware Update) or CLI
  7. 7. Follow the upgrade procedure to install 24.1R4
  8. 8. After upgrade, verify the Junos Space version shows 24.1R4 or later in the web UI
Caveat Standard upgrade risks apply - ensure backups are verified before proceeding; review release notes for any specific migration considerations

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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