dbcve.org
Appium\/base DriverApplication · Appium

CVE-2026-58191

MEDIUM · 6.1 CVSS v3.1 Published 2026-07-08
Fix available
A fix is available. Upgrade to 10.7.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Public exploit Remotely reachable No privileges 6 weeks old

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
Appium is a cross-platform automation framework for all kinds of apps, built on top of the W3C WebDriver protocol. Prior to 10.7.0, Appium's base-driver unconditionally mounts the /test/guinea-pig, /test/guinea-pig-scrollable, and /test/guinea-pig-app-banner routes, and compileLodashTemplate reflects the throwError query parameter, comments POST field, and User-Agent request header into HTML without escaping, allowing reflected cross-site scripting and arbitrary JavaScript execution on the server origin. This issue is fixed in version 10.7.0.

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

Appium's base-driver exposes test endpoints (/test/guinea-pig, /test/guinea-pig-scrollable, /test/guinea-pig-app-banner) that reflect the throwError query parameter, comments POST field, and User-Agent header into HTML via compileLodashTemplate without proper escaping, allowing reflected XSS and arbitrary JavaScript execution on the server origin.

MitigationUpgrade Appium to version 10.7.0 or later to receive the fix that properly escapes user-supplied input in the template compilation function. If immediate upgrade is not feasible, consider disabling or restricting access to the affected test routes.

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
Appium\/base DriverApplication
Affected:< 10.7.0

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. Identify Appium base-driver installation
    Locate the Appium base-driver package in your environment (e.g., check node_modules/appium-base-driver, or run 'npm list @appium/base-driver' if npm is available)
    Affected if The base-driver package is present in your installation
  2. Determine installed base-driver version
    Check the version of @appium/base-driver (e.g., inspect package.json, or run 'npm list @appium/base-driver --depth=0', or check the driver's about/version endpoint if exposed)
    Affected if The installed version is lower than 10.7.0 (e.g., 10.6.x, 10.5.x, etc.)
  3. Identify exposed test endpoints
    Review your Appium server configuration and routing setup to determine if the /test/guinea-pig, /test/guinea-pig-scrollable, and /test/guinea-pig-app-banner endpoints are registered and accessible
    Affected if Any of these test endpoints are exposed and reachable on the server
  4. Verify test route accessibility
    Attempt to access one of the test endpoints (e.g., send a GET request to http://<server>:<port>/test/guinea-pig) to confirm they respond
    Affected if The test endpoints respond with HTML content, indicating they are active
  5. Check input reflection behavior
    Send a request to an exposed test endpoint with a crafted query parameter (e.g., /test/guinea-pig?throwError=<script>alert(1)</script>) or a POST request with a comments field containing script content, and observe whether the input is reflected unescaped in the response
    Affected if User-supplied input appears in the response HTML without proper encoding/escaping

You are affected if Appium base-driver version is below 10.7.0 AND the test endpoints (/test/guinea-pig, /test/guinea-pig-scrollable, /test/guinea-pig-app-banner) are exposed and reflect user input without 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 10.7.0 or later
Fixed in 10.7.0
Interim mitigation

Upgrade Appium to version 10.7.0 or later to receive the fix that properly escapes user-supplied input in the template compilation function. If immediate upgrade is not feasible, consider disabling or restricting access to the affected test routes.

Recommended fix High confidence

10.7.0

  1. 1. Identify the current Appium base-driver version in use by checking package.json or running `npm list appium` or equivalent
  2. 2. Stop any running Appium server instances
  3. 3. Update Appium to version 10.7.0 or later using the package manager (e.g., `npm install [email protected]` or `pip install --upgrade Appium-Python-Client` if using Python bindings)
  4. 4. Verify the new version is installed correctly
  5. 5. Restart the Appium server and confirm the test endpoints are either removed or properly sanitizing input

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

Fix this in Appium\/base Driver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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