dbcve.org
Applitools EyesApplication · Jenkins

CVE-2025-53658

MEDIUM · 5.4 CVSS v3.1 Published 2025-07-09
Fix available
A fix is available. Upgrade to 1.16.6 or later.
See remediation →
58/100
Remediation priority · Elevated
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
Jenkins Applitools Eyes Plugin 1.16.5 and earlier does not escape the Applitools URL on the build page, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.

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

The Jenkins Applitools Eyes Plugin 1.16.5 and earlier does not properly escape the Applitools URL configuration value when rendering it on the build page, allowing stored XSS attacks. Attackers with Item/Configure permission can inject malicious JavaScript through the URL field that executes when other users view the build page.

MitigationUpgrade to a patched version of the Applitools Eyes Plugin that properly escapes URL output, or remove the plugin until a fix is available.

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
Applitools EyesApplication
Affected:< 1.16.6

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify if Applitools Eyes Plugin is installed
    Go to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Applitools Eyes' in the list of installed plugins. Alternatively, check the file system at $JENKINS_HOME/plugins for a folder named 'applitools-eyes' or similar.
    Affected if The plugin is installed and its version is 1.16.5 or earlier (check the plugin's manifest or the Manage Plugins UI for the exact version number)
  2. Determine the installed version of the plugin
    In Jenkins > Manage Jenkins > Manage Plugins > Installed tab, find the Applitools Eyes plugin and note the version column. Compare the version number against the affected range (versions before 1.16.6).
    Affected if The installed version is 1.16.5 or earlier, as these versions do not properly escape the URL configuration value
  3. Check if the plugin has been configured with an Applitools URL
    Navigate to a job that uses the Applitools Eyes plugin (or any job where the plugin is enabled), go to job configuration, and look for the Applitools Eyes section. Check if the 'Applitools URL' or similar URL field contains any value.
    Affected if The plugin is configured with an Applitools URL value, as the XSS vulnerability occurs when rendering this URL on the build page
  4. Inspect the configured URL for XSS payloads
    In the job configuration page where the Applitools URL is set, examine the URL field value. Look for common XSS patterns such as <script> tags, javascript: protocol handlers, event handlers like onload=, onerror=, or other HTML/script injection patterns.
    Affected if The configured URL contains any script injection attempts (script tags, javascript: prefix, or HTML event attributes) or if you suspect the URL has been tampered with by an unauthorized user with Item/Configure permission
  5. Verify user permissions for job configuration
    Review which users or groups have 'Item/Configure' permission for jobs that have the Applitools Eyes plugin enabled. Check job-level security settings or matrix-based security configurations in Jenkins.
    Affected if Users with Item/Configure permission (especially untrusted or non-admin users) can modify the Applitools URL, allowing them to inject malicious JavaScript that will execute for other users viewing the build page

You are affected if the Applitools Eyes Plugin version is 1.16.5 or earlier AND the plugin has been configured with an Applitools URL value that is rendered on the build page without proper escaping.

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 1.16.6 or later
Fixed in 1.16.6
Interim mitigation

Upgrade to a patched version of the Applitools Eyes Plugin that properly escapes URL output, or remove the plugin until a fix is available.

Recommended fix High confidence

1.16.6

  1. 1. Navigate to Jenkins dashboard
  2. 2. Go to Manage Jenkins > Manage Plugins
  3. 3. Click on the 'Installed' tab
  4. 4. Find 'Applitools Eyes' plugin in the list
  5. 5. If update is available, click 'Update now' or download version 1.16.6 from the Jenkins plugin repository
  6. 6. Restart Jenkins to complete the upgrade
  7. 7. Verify the plugin shows version 1.16.6 or later in the installed plugins list

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

Fix this in Applitools Eyes Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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