dbcve.org
Applitools EyesApplication · Jenkins

CVE-2025-53743

MEDIUM · 5.3 CVSS v3.1 Published 2025-07-09
Fix available
A fix is available. Upgrade to 1.16.6 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 does not mask Applitools API keys displayed on the job configuration form, increasing the potential for attackers to observe and capture them.

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

Jenkins Applitools Eyes Plugin version 1.16.5 and earlier renders Applitools API keys as plain text on the job configuration form instead of masking them as password-type fields, allowing users with access to job configurations to view and capture these credentials.

MitigationUpdate to a patched version of the plugin when released. In the meantime, restrict access to job configuration pages to trusted users only and rotate any exposed API keys as a precaution.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 inspect the directory $JENKINS_HOME/plugins/ for the applitools-eyes folder
    Affected if The plugin folder exists or is listed in the installed plugins
  2. Check the installed version
    In the Jenkins plugin manager, view the version column for Applitools Eyes plugin. Alternatively, read the file $JENKINS_HOME/plugins/applitools-eyes/META-INF/MANIFEST.MF and find the Implementation-Version attribute
    Affected if The version is 1.16.5 or earlier (anything less than 1.16.6)
  3. Identify jobs using Applitools Eyes
    Navigate to each job's configuration page (Job Name > Configure) and look for the 'Applitools Eyes' build step section. Alternatively, search Jenkins configuration XML files in $JENKINS_HOME/jobs/ for 'applitools' references
    Affected if At least one job has the Applitools Eyes build step configured
  4. Verify credential exposure in job configuration
    Open a job configuration page that uses Applitools Eyes and observe whether the API Key field displays in plain text (readable characters) rather than masked with dots or asterisks
    Affected if The API Key field shows plain text characters instead of password masking

You are affected if the Applitools Eyes plugin version is 1.16.5 or earlier AND you have jobs configured with Applitools Eyes that display API keys as plain text.

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

Update to a patched version of the plugin when released. In the meantime, restrict access to job configuration pages to trusted users only and rotate any exposed API keys as a precaution.

Recommended fix High confidence

Applitools Eyes Plugin version 1.16.6

  1. Navigate to the Jenkins dashboard
  2. Go to Manage Jenkins
  3. Click on Manage Plugins
  4. Select the Installed tab
  5. Locate the Applitools Eyes plugin in the list
  6. Check for update to version 1.16.6 or later
  7. Apply the upgrade and restart Jenkins if required
  8. Verify that API keys are now masked in job configuration forms

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
  • Implementation3.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,070
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,712.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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