dbcve.org
Waap CloudApplication · Ubikasec

CVE-2023-26261

CRITICAL · 9.8 CVSS v3.1 Published 2023-03-08
Fix available
A fix is available. Upgrade to 6.5.6 / 6.11.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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
In UBIKA WAAP Gateway/Cloud through 6.10, a blind XPath injection leads to an authentication bypass by stealing the session of another connected user. The fixed versions are WAAP Gateway & Cloud 6.11.0 and 6.5.6-patch15.

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

UBIKA WAAP Gateway/Cloud versions through 6.10 contain a blind XPath injection vulnerability in the authentication subsystem. This flaw allows unauthenticated attackers to extract session tokens of legitimate users by manipulating XPath queries, effectively bypassing authentication and hijacking existing sessions.

MitigationUpgrade UBIKA WAAP Gateway/Cloud to version 6.11.0 or 6.5.6-patch15. Additionally, monitor for unauthorized session activity and consider force-logout of all active sessions immediately after applying the patch.

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
Waap CloudApplication
Affected:< 6.11.0< 6.5.6= 6.5.6
Waap GatewayApplication
Affected:< 6.11.0< 6.5.6= 6.5.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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 product and version
    Locate the installed Ubikasec WAAP version (Cloud or Gateway) using the system administration interface, command-line tool, or version file typically found in /opt/ubika or via 'ubika-waap --version' if available
    Affected if The installed version is less than 6.11.0 or equals 6.5.6
  2. Confirm authentication subsystem is accessible
    Verify the WAAP login portal or authentication API endpoint is reachable from the network. Check the web interface URL or API endpoint for the login page
    Affected if The authentication interface is exposed externally or on an accessible network segment
  3. Review authentication logs for XPath injection patterns
    Examine authentication and application logs for unusual XPath syntax in login parameters, such as quote characters, or conditions like 'or', '1=1', or other XPath injection indicators in authentication requests
    Affected if Log entries show XPath injection attempts or malformed XPath queries in authentication logs
  4. Check for unauthorized session activity
    Review active sessions and session logs for concurrent or unexpected sessions, particularly from different IP addresses, or sessions created without corresponding failed login attempts
    Affected if Sessions exist that were not originated from legitimate login attempts or show suspicious originating IPs

A user is affected if the WAAP version is less than 6.11.0 or exactly 6.5.6 AND the authentication subsystem is accessible to potential attackers.

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 6.5.6 / 6.11.0 or later
Fixed in 6.5.66.11.0
Interim mitigation

Upgrade UBIKA WAAP Gateway/Cloud to version 6.11.0 or 6.5.6-patch15. Additionally, monitor for unauthorized session activity and consider force-logout of all active sessions immediately after applying the patch.

Recommended fix High confidence

Upgrade to Waap Cloud/Gateway 6.11.0 or 6.5.6-patch15 (for the 6.5.x branch)

  1. 1. Identify the current installed version of Waap Cloud or Waap Gateway by checking the system dashboard or using the version check command provided in the documentation
  2. 2. If currently running version 6.5.6, upgrade to version 6.5.6-patch15 (the patch release for the 6.5.x branch)
  3. 3. If running any version below 6.5.6 or between 6.5.6 and 6.11.0, upgrade to version 6.11.0 (the next major/minor release)
  4. 4. Follow the standard upgrade procedure documented at documentation.ubikasec.com for your deployment type (Cloud or Gateway)
  5. 5. After upgrade, verify that the authentication mechanism is functioning correctly and that the XPath injection vulnerability is no longer present
  6. 6. Review session management to ensure no existing sessions were compromised during the vulnerability window
Caveat Review release notes for 6.11.0 to check for any configuration or behavioral changes that may affect your deployment

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

Fix this in Waap Cloud Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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