dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-1630

MEDIUM · 5.1 CVSS v4.0 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/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
WEBCON BPS is vulnerable to Reflected XSS via one of parameters used by "/openinmobileapp" endpoint. An attacker can send a specially crafted URL that, when opened by an authenticated user, results in arbitrary JavaScript execution in the victim's browser. This issue was fixed in versions 2026.1.3.109 and 2025.2.1.293.

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

WEBCON BPS contains a reflected XSS vulnerability in the /openinmobileapp endpoint. An attacker can embed malicious JavaScript into URL parameters; when an authenticated user clicks the crafted link, the script executes in their browser within the application's context, potentially allowing session hijacking or data theft.

MitigationUpgrade WEBCON BPS to version 2026.1.3.109 or 2025.2.1.293 or later. Until patched, users should avoid clicking untrusted links, particularly those appearing to come from the application.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm WEBCON BPS installation
    Check for the WEBCON BPS installation directory (typically C:\Program Files\WEBCON\BPS or C:\Inetpub\WEBCON\BPS) or look for the WEBCON BPS service in Windows Services.
    Affected if WEBCON BPS is not installed on the system.
  2. Identify installed WEBCON BPS version
    Check the version information in the installation folder, typically in a version.txt file, or check the assembly version of the main WEBCON BPS DLLs. You can also query the Windows Registry under HKLM\SOFTWARE\WOW6432Node\WEBCON\BPS for the Version value.
    Affected if The version cannot be determined or is not listed.
  3. Compare version against fixed releases
    If version is determined, compare it against the fixed versions: 2026.1.3.109 and 2025.2.1.293. Versions lower than 2025.2.1.293 or between 2025.2.1.293 and 2026.1.3.109 are vulnerable.
    Affected if Installed version is below 2026.1.3.109 and also below 2025.2.1.293, or falls in the gap between 2025.2.1.293 and 2026.1.3.109.
  4. Verify mobile app endpoint accessibility
    Attempt to access the /openinmobileapp endpoint on your WEBCON BPS server (e.g., https://yourserver.com/openinmobileapp). The endpoint typically requires authentication.
    Affected if The endpoint is reachable and responds (indicating the vulnerable code path exists in the application).

Your environment is affected if WEBCON BPS is installed with a version lower than 2026.1.3.109 (or lower than 2025.2.1.293 if on the 2025 release train), and the /openinmobileapp endpoint is accessible to authenticated users.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade WEBCON BPS to version 2026.1.3.109 or 2025.2.1.293 or later. Until patched, users should avoid clicking untrusted links, particularly those appearing to come from the application.

Recommended fix Moderate confidence

2026.1.3.109 or 2025.2.1.293

  1. Identify current WEBCON BPS version in use
  2. Plan upgrade to one of the fixed releases: 2026.1.3.109 or 2025.2.1.293
  3. Schedule maintenance window for the upgrade
  4. Backup database and configuration files
  5. Upgrade WEBCON BPS to the chosen fixed version
  6. Verify the upgrade was successful and the /openinmobileapp endpoint is functioning correctly
  7. Test that the XSS vulnerability is no longer present

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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