dbcve.org
XplatformApplication · Tobesoft

CVE-2021-26626

HIGH · 8.8 CVSS v3.1 Published 2022-04-19
Fix available
A fix is available. Upgrade to 9.2.2.280 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Improper input validation vulnerability in XPLATFORM's execBrowser method can cause execute arbitrary commands. IF the second parameter value of the execBrowser function is ‘default’, the first parameter value could be passed to the ShellExecuteW API. The passed parameter is an arbitrary code to be executed. Remote attackers can use this vulnerability to execute arbitrary remote code.

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

XPLATFORM's execBrowser method has improper input validation that allows arbitrary command execution. When the second parameter is set to 'default', the first parameter value is passed directly to the Windows ShellExecuteW API without sanitization, enabling remote code execution.

MitigationImplement strict input validation on the execBrowser method parameters to reject or sanitize any shell metacharacters before passing to ShellExecuteW. Consider implementing an allowlist of permitted values/URLs and disabling the 'default' mode if not required.

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
XplatformApplication
Affected:< 9.2.2.280

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 Xplatform installation and version
    Locate Tobesoft Xplatform runtime or development installation directories (common paths: C:\Program Files\Tobesoft\Xplatform, C:\Users\[user]\AppData\Local\Tobesoft). Check the version by examining version info in executable files (Xplatform.dll, Xplatform.exe) or version.xml/readme.txt
    Affected if Installed version is lower than 9.2.2.280
  2. Find application source files using execBrowser
    Search project directories for .xpl, .xapl, .xsrc or compiled application files that contain the string 'execBrowser'. On Windows, use: findstr /s /i "execBrowser" *.xpl *.xapl *.xsrc 2>nul or use a code search tool across the application source tree
    Affected if The execBrowser method is present in application code
  3. Verify vulnerable parameter configuration
    Examine each execBrowser call found. Check if the second parameter is set to the literal string 'default' (case-sensitive). Review function calls like execBrowser(url, 'default') or similar syntax in the Xplatform script files
    Affected if The second parameter of execBrowser is set to 'default' (this is the vulnerable configuration)
  4. Check for external input flow to execBrowser
    Trace data flow in application code to determine if the first parameter (passed to ShellExecuteW) can be influenced by external sources (user input, file content, network data). Look for patterns where execBrowser receives variables rather than hardcoded strings
    Affected if The first parameter of execBrowser accepts unsanitized external input and uses 'default' mode

User is affected if running Tobesoft Xplatform version below 9.2.2.280 AND their application code calls execBrowser with 'default' as the second parameter, allowing unsanitized input to reach Windows ShellExecuteW.

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

Implement strict input validation on the execBrowser method parameters to reject or sanitize any shell metacharacters before passing to ShellExecuteW. Consider implementing an allowlist of permitted values/URLs and disabling the 'default' mode if not required.

Recommended fix Moderate confidence

XPLATFORM version 9.2.2.280 or later

  1. Identify all systems running XPLATFORM versions prior to 9.2.2.280
  2. Obtain the updated XPLATFORM version 9.2.2.280 or later from the official vendor
  3. Backup all current configurations and data for the XPLATFORM installation
  4. Deploy the updated XPLATFORM 9.2.2.280 to all affected systems
  5. Verify the execBrowser function now properly validates input before passing to ShellExecuteW API
  6. Test that the application functionality remains intact after the update

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

Fix this in Xplatform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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