dbcve.org
Junos SpaceApplication · Juniper

CVE-2025-60001

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 Generate Report page 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 · moderate confidence

This is a stored (persistent) cross-site scripting (XSS) vulnerability in Juniper Junos Space's Generate Report page. An authenticated attacker can inject malicious script tags into report parameters that persist on the page. When other users (including administrators) subsequently view or access these reports, the injected JavaScript executes in their browser context, enabling the attacker to perform actions with the victim's privileges.

MitigationUpgrade Junos Space to version 24.1R4 or later. Additionally, implement output encoding and input validation on the Generate Report page to prevent script injection.

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
    Access the Junos Space web UI and navigate to the admin or system information page to view the installed version, or use the CLI command 'show version' if available via SSH
    Affected if The installed version is 24.1 or any version lower than 24.1 (versions prior to 24.1R4 are affected)
  2. Verify Generate Report feature access
    Log into Junos Space as an authenticated user and navigate to the Generate Report page or reporting section to confirm the feature is accessible
    Affected if The Generate Report page is accessible and functional in the environment
  3. Inspect saved report configurations for script content
    Review any saved report templates or scheduled reports in the Junos Space reporting interface for unexpected or encoded script tags in report name, description, or parameter fields
    Affected if Unexpected script tags (<script>, javascript:, onload=, onerror=, etc.) are found in report parameters or saved report configurations
  4. Check browser execution context
    When viewing existing reports in the Junos Space UI, inspect the page source or use browser developer tools to examine if user-supplied report fields are rendered with proper encoding
    Affected if Report fields are rendered without HTML encoding, allowing script execution in the browser

The environment is affected if Junos Space version is 24.1 or below and the Generate Report page is in use, with any stored report parameters containing unsanitized script content that could execute when viewed by other 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. Additionally, implement output encoding and input validation on the Generate Report page to prevent script injection.

Recommended fix High confidence

24.1R4

  1. Download Junos Space version 24.1R4 from the Juniper support portal at supportportal.juniper.net
  2. Review the Junos Space upgrade documentation for your current version
  3. Create a complete backup of the Junos Space database and configuration
  4. Schedule a maintenance window as the upgrade may require downtime
  5. Upload the 24.1R4 upgrade image to the Junos Space appliance
  6. Execute the upgrade following the documented procedure for your platform
  7. Verify the upgrade completed successfully and the Generate Report page functions correctly
  8. Confirm the system is running version 24.1R4 or later

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 / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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