CVE-2025-59986
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 · uneditedAn 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 input fields in Model Devices 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 confidenceStored XSS vulnerability in Junos Space's Model Devices feature allows attackers to inject malicious script into input fields. When other users (including administrators) view these fields, the script executes with the victim's privileges, enabling command execution.
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< 24.1= 24.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Junos Space installation and versionLocate the Junos Space management interface (typically web-based) or check system documentation for the installed version. Common methods include: accessing the web UI and viewing the About/Version page, or checking the installed packages via system commands if you have CLI access.Affected if The installed version is 24.1 or any version prior to 24.1 (any version < 24.1)
-
Verify Model Devices feature is accessibleNavigate to or enumerate the Model Devices feature within the Junos Space web interface. This feature is typically found in the device management or provisioning sections.Affected if The Model Devices feature exists and is accessible to users in the environment
-
Inspect Model Devices input fields for injected scriptsAccess the Model Devices feature and examine all input fields (device names, descriptions, configuration fields, custom attributes). Look for any existing entries containing script tags, javascript: URIs, or other XSS payloads in these fields.Affected if Any input fields in Model Devices contain unsanitized script content (script tags, event handlers, javascript: prefixes, or encoded variants)
-
Check user session behavior when accessing Model DevicesAs a test administrator, access the Model Devices section and observe if any unexpected JavaScript executes, redirects occur, or console errors appear when viewing device records with populated fields.Affected if JavaScript executes automatically when viewing device records in Model Devices, indicating stored XSS is present
You are affected if your Junos Space version is 24.1 or any version below 24.1 AND the Model Devices feature is accessible and contains or could contain crafted input with malicious script content.
Generated from the published advisory. Verify against your own configuration.
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 · scoped24.1
Upgrade to Junos Space 24.1R4 or later to resolve the improper input neutralization. Until patched, restrict access to Model Devices and monitor for suspicious script injection in input fields.
24.1R4
- 1. Log into the Junos Space web management interface
- 2. Navigate to the Administration section or check for available updates
- 3. Locate the Junos Space firmware upgrade option
- 4. Download and apply Junos Space version 24.1R4 which contains the fix for this XSS vulnerability
- 5. After upgrade, verify that the Model Devices input fields properly sanitize HTML/script tags
- 6. Confirm the upgrade was successful and test that the XSS vulnerability is no longer exploitable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59986 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-59986 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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