dbcve.org
Paragon AutomationApplication · Juniper

CVE-2025-52987

MEDIUM · 6.1 CVSS v3.1 Published 2026-01-15
Fix available
A fix is available. Upgrade to 24.1.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
A clickjacking vulnerability exists in the web portal of Juniper Networks Paragon Automation (Pathfinder, Planner, Insights) due to the application's failure to set appropriate X-Frame-Options and X-Content-Type HTTP headers. This vulnerability allows an attacker to trick users into interacting with the interface under the attacker's control.  This issue affects all versions of Paragon Automation (Pathfinder, Planner, Insights) before 24.1.1.

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 clickjacking vulnerability in Juniper Paragon Automation where the web portal fails to set X-Frame-Options and X-Content-Type-Options HTTP headers, allowing the application to be embedded in iframes on attacker-controlled pages. Attackers can overlay invisible or disguised interface elements to trick authenticated users into performing unintended actions.

MitigationConfigure the web server or application to include X-Frame-Options: DENY or SAMEORIGIN and X-Content-Type-Options: nosniff headers in all HTTP responses, or upgrade to version 24.1.1 or later.

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
Paragon AutomationApplication
Affected:< 24.1.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 Juniper Paragon Automation deployment
    Identify whether Juniper Paragon Automation is installed in your environment and locate its web portal URL (typically accessible on port 443 or 8443). Check with your system administrator or review network service listings.
    Affected if Juniper Paragon Automation web portal is accessible and running in your environment
  2. Check installed version
    Determine the installed version of Juniper Paragon Automation by accessing the web UI admin panel, checking /opt/juniper/version files, or using CLI commands such as 'pkg show' or 'version' if you have shell access. Compare against the affected range: versions prior to 24.1.1 are vulnerable.
    Affected if Installed version is lower than 24.1.1 (e.g., 24.1.0, 23.x, or earlier releases)
  3. Inspect HTTP responses for X-Frame-Options header
    Send an HTTP GET request to the Paragon Automation web portal URL using a tool like curl: curl -I https://your-paragon-host.com. Examine the response headers for the presence of X-Frame-Options.
    Affected if X-Frame-Options header is absent from HTTP responses, allowing the site to be embedded in iframes
  4. Inspect HTTP responses for X-Content-Type-Options header
    Send an HTTP GET request to the Paragon Automation web portal URL and examine response headers for X-Content-Type-Options. Example: curl -I https://your-paragon-host.com.
    Affected if X-Content-Type-Options header is absent from HTTP responses, allowing MIME type sniffing attacks

You are affected if Juniper Paragon Automation version is below 24.1.1 AND the web portal HTTP responses are missing either X-Frame-Options or X-Content-Type-Options headers.

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.1 or later
Fixed in 24.1.1
Interim mitigation

Configure the web server or application to include X-Frame-Options: DENY or SAMEORIGIN and X-Content-Type-Options: nosniff headers in all HTTP responses, or upgrade to version 24.1.1 or later.

Recommended fix High confidence

24.1.1

  1. 1. Identify the current version of Paragon Automation by accessing the web interface or using the CLI command: show version
  2. 2. Verify the installation is affected by checking the X-Frame-Options and X-Content-Type-Options headers using browser developer tools or curl: curl -I https://<paragon-host>
  3. 3. If headers are missing or set to 'DENY' or 'SAMEORIGIN' is absent, the system is vulnerable
  4. 4. Schedule a maintenance window for the upgrade
  5. 5. Create a backup of the current Paragon Automation configuration
  6. 6. Download Paragon Automation version 24.1.1 or later from the Juniper support portal (supportportal.juniper.net)
  7. 7. Perform the upgrade following the official Juniper upgrade documentation for Paragon Automation
  8. 8. After upgrade, verify the fix by checking that X-Frame-Options: DENY or X-Frame-Options: SAMEORIGIN is present in HTTP responses
Caveat Standard upgrade precautions apply - review release notes for any configuration or compatibility changes before proceeding

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

Fix this in Paragon Automation Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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