dbcve.org
Applitools EyesApplication · Jenkins

CVE-2025-53742

MEDIUM · 6.5 CVSS v3.1 Published 2025-07-09
Fix available
A fix is available. Upgrade to 1.16.6 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 stores Applitools API keys unencrypted in job config.xml files on the Jenkins controller, where they can be viewed by users with Item/Extended Read permission or access to the Jenkins controller file system.

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 versions 1.16.5 and earlier stores Applitools API keys in plaintext within job config.xml files. This exposes credentials to any user with Item/Extended Read permission on jobs or anyone with filesystem access to the Jenkins controller, representing a sensitive data exposure vulnerability.

MitigationMigrate existing API keys from config.xml files to Jenkins' built-in credentials store, which encrypts secrets at rest. Users should rotate exposed API keys immediately and update jobs to reference credentials from the secure store rather than storing them in plain text.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Verify Applitools Eyes Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Applitools Eyes', or run: jenkins-cli.jar who-is-online (or check $JENKINS_HOME/plugins for applitools-eyes folder)
    Affected if Plugin version is 1.16.5 or earlier (check the .jpi or .hpi file's manifest for the Version attribute)
  2. Identify jobs using Applitools Eyes
    Search job config.xml files for '<applitools>' or 'ApplitoolsEyes' elements: find $JENKINS_HOME/jobs -name config.xml -exec grep -l -i 'applitools' {} \;
    Affected if Any config.xml files contain Applitools-related configuration blocks
  3. Inspect job config.xml for plaintext API keys
    Examine the contents of identified config.xml files, looking for the 'apiKey' or 'apiKey' field under applitools configuration sections: cat $JENKINS_HOME/jobs/JOBNAME/config.xml | grep -i apikey
    Affected if The API key value appears as plain, unencrypted text (not wrapped in {crypted} or similar jenkins encryption tags)
  4. Compare plugin version against affected range
    Review the plugin version from step 1 against the vulnerable range: affected if version < 1.16.6
    Affected if Installed plugin version is 1.16.5 or earlier

User is affected if Applitools Eyes Plugin version 1.16.5 or earlier is installed AND any job config.xml files contain plaintext (unencrypted) API key values under applitools configuration sections.

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

Migrate existing API keys from config.xml files to Jenkins' built-in credentials store, which encrypts secrets at rest. Users should rotate exposed API keys immediately and update jobs to reference credentials from the secure store rather than storing them in plain text.

Recommended fix High confidence

1.16.6

  1. Log in to Jenkins as an administrator
  2. Navigate to 'Manage Jenkins' > 'Manage Plugins'
  3. Go to the 'Updates' tab
  4. Locate 'Applitools Eyes Plugin' in the list
  5. Select the checkbox next to the plugin
  6. Click 'Download now and install after restart'
  7. Wait for the download to complete
  8. Restart Jenkins (or wait for the scheduled restart)

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

Fix this in Applitools Eyes Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing1.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,270
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,032.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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