dbcve.org
Junos SpaceApplication · Juniper

CVE-2025-59985

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 a field on the Purging Policy 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 · high confidence

A stored cross-site scripting (XSS) vulnerability in Juniper Networks Junos Space allows attackers to inject malicious script tags into a field on the Purging Policy page. When other users (including administrators) visit or interact with the affected page, the injected JavaScript executes with the victim's permissions, potentially enabling command execution.

MitigationUpgrade Junos Space to version 24.1R4 or later to obtain the vendor patch. As a compensating control, restrict access to the Purging Policy page to trusted administrators only until the upgrade is applied.

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. Confirm Junos Space is installed
    Access the Junos Space web management interface or check system processes/services for 'Junos Space' running on the device.
    Affected if Junos Space software is present on the system.
  2. Identify the Junos Space version
    Log into the Junos Space web UI, navigate to Administration > System > Platform and note the version shown. Alternatively, access the CLI and run: `show version` or `system information` command.
    Affected if The installed version is 24.1 or any version lower than 24.1 (for example, 24.0.x, 23.x, 22.x, etc.).
  3. Verify access to the Purging Policy page
    In the Junos Space web UI, navigate to the Purging Policy configuration area (typically under Administration > Data Management > Purging Policy or similar path depending on version).
    Affected if The Purging Policy page is accessible and the user can view or modify policy settings.
  4. Confirm user role and page interaction
    Check if the current user account has permissions to access the Purging Policy page. Note that both regular users and administrators who interact with this page would be affected if malicious script is already stored.
    Affected if Any user with access to the Purging Policy page exists in the system, as the stored XSS would execute when they visit that page.

A system is affected if Junos Space version is 24.1 or any version below 24.1 AND the Purging Policy page is accessible to at least one user in the environment.

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. As a compensating control, restrict access to the Purging Policy page to trusted administrators only until the upgrade is applied.

Recommended fix High confidence

24.1R4

  1. Log in to Junos Space as an administrator
  2. Back up the current Junos Space configuration and data
  3. Download Junos Space 24.1R4 from the Juniper support portal
  4. Upload the upgrade package to Junos Space
  5. Follow the Junos Space upgrade procedure to apply version 24.1R4
  6. Verify the upgrade was successful and the version is 24.1R4
  7. Test the Purging Policy page to confirm the XSS vulnerability is remediated
Caveat Standard Junos Space upgrade considerations apply - ensure backup before upgrading

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

Fix this in Junos Space Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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