dbcve.org
Space Security DirectorApplication · Juniper

CVE-2025-59974

HIGH · 8.4 CVSS v3.1 Published 2025-10-09
Fix available
A fix is available. Upgrade to 24.1 or later.
See remediation →
88/100
Remediation priority · High
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 Junos Space Security Director allows an attacker to inject malicious scripts into the application, which are then stored and executed in the context of other users' browsers when they access affected pages.This issue affects Juniper Security Director:  * All versions 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

This is a stored Cross-Site Scripting (XSS) vulnerability in Junos Space Security Director where an attacker can inject malicious JavaScript payloads into the application. The malicious scripts are persisted in the database and executed in the context of other users' browsers when they access affected pages, allowing session hijacking, credential theft, or defacement.

MitigationUpgrade Junos Space Security Director to version 24.1R4 or later to remediate the stored XSS 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
Space Security DirectorApplication
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
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Check Junos Space Security Director version
    Log into Junos Space and navigate to the Security Director application. Go to Administration > System > Software Updates or check the main dashboard for the Security Director version information. Alternatively, use the CLI command 'show version' on the Junos Space appliance and cross-reference with the Security Director patch level.
    Affected if The installed version is 24.1 or any version prior to 24.1 (for example, 23.4, 23.3, etc.)
  2. Confirm Security Director is active
    Access the Junos Space web UI and verify that the Security Director dashboard is accessible and loaded. Navigate to Security Director > Dashboard to confirm the module is enabled and running.
    Affected if Security Director is deployed and accessible to users
  3. Identify user input fields in Security Director
    Browse through Security Director sections such as Policy Management, Object Configuration, or User Management. Look for input fields where users can create or modify security policies, objects, or configurations that get stored in the database.
    Affected if User-accessible input fields exist that accept and persist data to the database
  4. Audit for existing malicious scripts (optional)
    If already compromised, query the Junos Space database (via support access) for suspicious script tags or JavaScript patterns in tables related to Security Director configurations, policy objects, or custom profiles.
    Affected if Malicious script content is found stored in Security Director-related database tables

You are affected if Junos Space Security Director version is 24.1 or any version below 24.1R4, and the Security Director module is enabled and 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 Security Director to version 24.1R4 or later to remediate the stored XSS vulnerability.

Recommended fix High confidence

24.1R4

  1. 1. Back up the Junos Space Security Director configuration before initiating the upgrade.
  2. 2. Review Junos Space upgrade documentation and release notes for 24.1R4 for any prerequisites.
  3. 3. Download Junos Space Security Director version 24.1R4 or later from the Juniper support portal.
  4. 4. Initiate the upgrade through the Junos Space web interface or CLI, following standard upgrade procedures.
  5. 5. Verify the upgrade completed successfully by logging into Security Director.
  6. 6. Confirm the Security Director version reflects 24.1R4 or later.
  7. 7. Test critical Security Director workflows to ensure functionality is intact after upgrade.
Caveat Review Junos Space 24.1R4 release notes for any compatibility or migration considerations specific to your deployment

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

Fix this in Space Security Director 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-59974 — 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-59974 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