Saml Sso Service ProviderDrupal extension · Miniorange
CVE-2026-5343
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 · uneditedImproper Check for Unusual or Exceptional Conditions vulnerability in Drupal SAML SSO - Service Provider allows Privilege Escalation. This issue affects SAML SSO - Service Provider: from 0.0.0 before 3.1.4.
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 · moderate confidenceThe Drupal SAML SSO Service Provider module has an improper check for unusual or exceptional conditions in its SAML authentication handling, which can be exploited to gain elevated privileges beyond what the user's SAML identity should provide.
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 Sso Service ProviderDrupal extension
>= 3.0.1, < 3.1.4= 7.x-1.0= 7.x-1.1= 7.x-1.2= 7.x-1.3= 7.x-1.4= 7.x-1.5= 7.x-1.6= 7.x-1.7= 7.x-1.8= 7.x-1.9= 7.x-1.91CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed module versionCheck the miniorange_saml_sp module version by reviewing the module's info file (miniorange_saml_sp.info.yml for D8+ or miniorange_saml_sp.info for D7) located in the modules directory, or use Drush command: drush pm-list --type=module --status=enabled | grep miniorangeAffected if Version is >= 3.0.1 and < 3.1.4, or is any 7.x-1.x version from 1.0 through 1.91
-
Confirm SAML authentication is configuredReview the module configuration at /admin/config/people/saml/idp (or similar path under /admin/config/people/saml) to verify an Identity Provider is configured and the service provider is enabledAffected if SAML SSO authentication is actively configured and in use
-
Review IdP-to-Drupal role mappingsExamine the role mapping settings at /admin/config/people/saml/spur or the role mappings section in the SAML configuration page. Check which Drupal roles are mapped from SAML assertionsAffected if Role mappings exist that could be exploited through improper validation of exceptional conditions in SAML responses
The environment is affected if the miniorange_saml_sp module version falls within the affected ranges AND SAML authentication is configured, allowing potential privilege escalation via SAML response handling.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.1.4
Update the SAML SSO - Service Provider module to version 3.1.4 or later to obtain the fix for this privilege escalation vulnerability.
3.1.4
- Backup your Drupal site and database before making any changes
- Update the SAML SSO - Service Provider module to version 3.1.4 using Composer: composer require drupal/saml_sp ^3.1.4 --update-with-all-dependencies
- Run Drupal database updates: drush updatedb or via /update.php
- Clear Drupal caches: drush cr or via the admin interface
- Verify SAML SSO functionality by testing single sign-on
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Saml Sso Service Provider
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5343 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5343 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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