CVE-2025-52987
BaseFortify
Publication date: 2026-01-15
Last updated on: 2026-01-15
Assigner: Juniper Networks, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| juniper_networks | paragon_automation | to 24.1.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-1021 | The web application does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain, which can lead to user confusion about which interface the user is interacting with. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a clickjacking issue in the web portal of Juniper Networks Paragon Automation (Pathfinder, Planner, Insights). It occurs because the application does not set the appropriate X-Frame-Options and X-Content-Type HTTP headers. This allows an attacker to trick users into interacting with the web interface in a way controlled by the attacker.
How can this vulnerability impact me? :
The vulnerability can impact you by allowing attackers to deceive users into performing unintended actions on the Paragon Automation web portal. This could lead to unauthorized operations or manipulation of the system through the user's interaction with a maliciously crafted interface.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by checking if the Juniper Networks Paragon Automation web portal responses lack the appropriate X-Frame-Options and X-Content-Type HTTP headers. For example, you can use curl commands to inspect the HTTP headers: curl -I https://<paragon-automation-url> and look for the absence of X-Frame-Options and X-Content-Type headers.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating Juniper Networks Paragon Automation to version 24.1.1 or later, where the vulnerability is fixed. If updating is not immediately possible, consider implementing web server or proxy configurations to add appropriate X-Frame-Options and X-Content-Type headers to the HTTP responses to prevent clickjacking attacks.