dbcve.org
WorkbenchApplication · Salesforce

CVE-2026-34951

MEDIUM · 6.1 CVSS v3.1 Published 2026-04-06
Fix available
A fix is available. Upgrade to 65.0.0 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
Workbench is a suite of tools for administrators and developers to interact with Salesforce.com organizations via the Force.com APIs. Prior to 65.0.0, Workbench contains a reflected cross-site scripting vulnerability via the footerScripts parameter, which does not sanitize user-supplied input before rendering it in the page response. Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in Workbench allows XSS Targeting Error Pages. This vulnerability is fixed in 65.0.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

Workbench versions prior to 65.0.0 contain a reflected cross-site scripting (XSS) vulnerability. The footerScripts parameter does not sanitize user-supplied input before rendering it in page responses, allowing attackers to inject malicious scripts via the parameter, particularly when targeting error pages.

MitigationUpgrade Workbench to version 65.0.0 or later, which contains the fix for this XSS vulnerability.

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
WorkbenchApplication
Affected:< 65.0.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 the installed Workbench version
    Access the Workbench About page (usually at /workbench/about.php) or check the version identifier in the application's footer. If self-hosted, also check the version file in the installation directory.
    Affected if The version displayed is below 65.0.0 (for example, 64.x.x or earlier)
  2. Locate footerScripts parameter handling
    Search the Workbench source code for occurrences of 'footerScripts' to identify where this parameter is processed and rendered. Check PHP files that handle request parameters and page rendering.
    Affected if The application processes the footerScripts parameter without visible input sanitization or encoding before rendering it in page responses
  3. Test parameter reflection on error pages
    Craft a request to an error page (such as a 404 or 500 error page) including a test payload in the footerScripts parameter, for example: ?footerScripts=<script>alert('XSS')</script>. Observe if the script executes or is reflected as raw text in the response.
    Affected if The payload is reflected back without HTML encoding or sanitization, indicating the XSS vulnerability is present
  4. Verify the patch status
    Check if the installed version matches or exceeds the fixed version 65.0.0 by reviewing release notes or the current version identifier in the application.
    Affected if The installed version is prior to 65.0.0 and the application does not have a separate security patch applied

You are affected if Workbench version is below 65.0.0 and the footerScripts parameter is reflected without sanitization in page responses, particularly on error pages.

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

Upgrade Workbench to version 65.0.0 or later, which contains the fix for this XSS vulnerability.

Recommended fix High confidence

65.0.0

  1. 1. Identify the current version of Workbench deployed in your environment
  2. 2. Download Workbench version 65.0.0 or later from the official GitHub repository (github.com/forceworkbench/workbench)
  3. 3. Backup the current Workbench installation and any custom configurations
  4. 4. Upgrade the Workbench installation to version 65.0.0 by replacing the application files with the new version
  5. 5. Restart any application services to ensure the new version is loaded
  6. 6. Verify the upgrade was successful by confirming the Workbench version displays as 65.0.0 or later
  7. 7. Test that the footerScripts parameter is now properly sanitized and no longer accepts unsanitized input
Caveat Review the release notes for version 65.0.0 to check for any breaking changes or configuration differences from your current version

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

Fix this in Workbench Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,520
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,432.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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