dbcve.org
Saml Sp 2.0 Single Sign OnApplication · Drupal

CVE-2022-26493

HIGH · 8.8 CVSS v3.1 Published 2022-06-03
Fix available
A fix is available. Upgrade to after 8.x-2.24 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Xecurify's miniOrange Premium, Standard, and Enterprise Drupal SAML SP modules possess an authentication and authorization bypass vulnerability. An attacker with access to a HTTP-request intercepting method is able to bypass authentication and authorization by removing the SAML Assertion Signature - impersonating existing users and existing roles, including administrative users/roles. This vulnerability is not mitigated by configuring the module to enforce signatures or certificate checks. Xecurify recommends updating miniOrange modules to their most recent versions. This vulnerability is present in paid versions of the miniOrange Drupal SAML SP product affecting Drupal 7, 8, and 9.

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

The miniOrange Drupal SAML SP modules fail to properly validate SAML assertions when the signature is removed from the HTTP request. Even with signature enforcement configured, the module accepts unsigned assertions, allowing attackers to impersonate any user including administrators by modifying the SAML response.

MitigationUpdate to the latest version of miniOrange Drupal SAML SP modules (Premium, Standard, or Enterprise) for Drupal 7, 8, or 9 per Xecurify's recommendations.

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
Saml Sp 2.0 Single Sign OnApplication
Affected:>= 7.x, <= 7.x-2.57>= 8.x, <= 8.x-2.24

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 if miniOrange SAML SP module is installed
    Check Drupal modules directory for miniorange_saml_sp or mo_saml modules. Run: `find /path/to/drupal/modules -type d -name '*miniorange*' -o -name '*mo_saml*'` or inspect the Drupal database: `SELECT name, status FROM system WHERE name LIKE '%miniorange%' OR name LIKE '%saml%';`
    Affected if The module is present and enabled in Drupal
  2. Check installed module version
    Examine the module's info file: /path/to/drupal/modules/miniorange_saml_sp/miniorange_saml_sp.info.yml or query the system table: `SELECT schema_version FROM system WHERE name = 'miniorange_saml_sp';` Compare against affected ranges: Drupal 7: 7.x through 7.x-2.57; Drupal 8+: 8.x through 8.x-2.24
    Affected if Installed version falls within 7.x-2.57 or lower, or 8.x-2.24 or lower for the respective Drupal major versions
  3. Verify SAML Service Provider configuration is active
    Check if SAML IDP is configured in the module settings. Look for stored configuration: `SELECT * FROM variable WHERE name LIKE '%miniorange_saml%';` or inspect the module's config entity at /admin/config/services/saml/idp
    Affected if SAML SP is configured and communicating with an external Identity Provider (IDP)
  4. Inspect XML signature validation enforcement setting
    Review the module configuration at /admin/config/services/saml/spub (or similar path under /admin/config/ miniorange). Check for fields like 'Enforce Signature', 'Strict Mode', or 'Verify XML Signature' in the SAML settings. Query database: `SELECT * FROM config WHERE name LIKE '%miniorange_saml.settings%';`
    Affected if SAML authentication is enabled and module settings allow processing of SAML assertions (regardless of signature validation toggle state)

User is affected if the miniOrange SAML SP module is installed with version 7.x-2.57 or below (Drupal 7) or 8.x-2.24 or below (Drupal 8/9), and SAML authentication is configured as an active SP.

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 a release after 8.x-2.24
Interim mitigation

Update to the latest version of miniOrange Drupal SAML SP modules (Premium, Standard, or Enterprise) for Drupal 7, 8, or 9 per Xecurify's recommendations.

Recommended fix Moderate confidence

Latest available version of miniOrange Drupal SAML SP module (vendor recommends updating to most recent versions beyond 7.x-2.57 and 8.x-2.24)

  1. Identify the currently installed miniOrange Drupal SAML SP module version using Drupal's module management interface or command line tools
  2. Access the miniOrange customer portal or Drupal.org project page to obtain the latest available version of the miniOrange SAML SP module
  3. Review the release notes/changelog for the latest version to confirm security fixes for CVE-2022-26493
  4. Backup the Drupal database and files before performing the upgrade
  5. Update the miniOrange SAML SP module to the latest version using Drupal's module update process (drush up or manual upload)
  6. Clear Drupal caches after the update to ensure the new module code is loaded
  7. Verify the module configuration is intact and test SAML authentication to confirm the fix is working

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

Fix this in Saml Sp 2.0 Single Sign On Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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