CVE-2025-60009
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 CLI Configlet 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 confidenceA stored XSS vulnerability exists in Junos Space's CLI Configlet page where improper input validation allows attackers to inject malicious script tags. When other users (including administrators) visit the affected page, the injected scripts execute with the victim's permissions, potentially enabling command execution and privilege escalation.
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.
-
Verify Junos Space versionAccess the Junos Space web UI and navigate to Administration > Software. Alternatively, run 'show version' via the CLI or check /var/home/public/ssp/etc/version file if accessible. Compare the installed version against the affected ranges: versions < 24.1 or exactly 24.1 are vulnerable.Affected if The installed Junos Space version is < 24.1 or equals 24.1 exactly.
-
Confirm CLI Configlet feature accessNavigate to the CLI Configlet page in the Junos Space web UI (typically under Devices > Configlets or a similar path). Determine if this functionality is accessible to any user accounts.Affected if CLI Configlet page is accessible and users can create or edit configlets.
-
Inspect existing configlets for injected scriptsReview all user-created configlets in the CLI Configlet section. Look for <script> tags, javascript: URIs, or other potentially malicious code within configlet definitions.Affected if Any configlet contains script tags or suspicious JavaScript code that was not intentionally added by an administrator.
-
Check audit logs for CLI Configlet activityReview Junos Space audit logs (typically found under Administration > Audit Logs) for entries related to CLI Configlet creation, modification, or execution. Look for unexpected or unauthorized changes.Affected if Audit logs show configlet modifications by unexpected users or at unusual times.
-
Review user accounts with configlet permissionsExamine user roles and permissions (Administration > Users/Roles) to identify which accounts have access to the CLI Configlet functionality.Affected if Untrusted or unauthorized user accounts have permissions to create or modify configlets.
A user is affected if Junos Space version is less than 24.1 or exactly 24.1 AND the CLI Configlet feature is accessible and contains unexpected script content or has been modified by unauthorized users.
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 Junos Space to version 24.1R4 or later. Until the upgrade can be applied, restrict access to the CLI Configlet functionality to only trusted administrators and monitor for suspicious activity.
Junos Space 24.1R4 or later
- Check the current Junos Space version by navigating to Admin > System > Software Updates or using the CLI command 'show version'
- Review Juniper Networks Junos Space upgrade documentation and release notes for 24.1R4
- Plan and schedule the upgrade during a maintenance window to minimize business impact
- Back up the current Junos Space configuration and database
- Download Junos Space 24.1R4 or later from the Juniper support portal
- Follow Juniper's documented upgrade procedure to apply the 24.1R4 release
- Verify the upgrade was successful and the version is 24.1R4 or later
- Test the CLI Configlet functionality to confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-60009 — 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-60009 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