dbcve.org
SamlTYPO3 extension · Miniorange

CVE-2021-36786

HIGH · 7.5 CVSS v3.1 Published 2021-08-13
Fix available
A fix is available. Upgrade to 1.4.3 or later.
See remediation →
84/100
Remediation priority · High
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
The miniorange_saml (aka Miniorange Saml) extension before 1.4.3 for TYPO3 allows Sensitive Data Exposure of API credentials and private keys.

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 confidence

The miniorange_saml TYPO3 extension before version 1.4.3 contains a vulnerability that allows exposure of API credentials and private keys, potentially enabling unauthorized access to SAML Single Sign-On configurations.

MitigationUpgrade the miniorange_saml extension to version 1.4.3 or later to remediate the sensitive data exposure. Review and rotate any credentials that may have been compromised.

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
SamlTYPO3 extension
Affected:< 1.4.3

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed version of miniorange_saml extension
    In TYPO3 backend, navigate to Admin Tools > Extensions > miniorange_saml and view the version number displayed, or use CLI: typo3cms extension:list | grep miniorange_saml
    Affected if Installed version is lower than 1.4.3 (e.g., 1.4.2, 1.4.1, 1.4.0, or any version before 1.4.3)
  2. Verify SAML configuration exists
    Check if the miniorange_saml extension has been configured with a Service Provider (SP) or Identity Provider (IdP) settings. Navigate to the extension module in TYPO3 backend to see if any SAML configurations are present.
    Affected if SAML configuration is present and contains API credentials, private keys, or SAML certificates stored within the extension settings
  3. Inspect extension configuration files
    Check the extension configuration directory for miniorange_saml. Look for configuration files in typo3conf/ext/miniorange_saml/ that may contain unencrypted credentials, API keys, or private key files.
    Affected if Configuration files contain plaintext API credentials, private keys, or sensitive SAML metadata that should not be publicly accessible
  4. Check for publicly accessible configuration
    Review web server logs and examine if the extension configuration directory or any configuration XML/JSON files are accessible via HTTP/HTTPS without authentication.
    Affected if Configuration files or credentials are accessible via direct URL access without authentication

You are affected if the miniorange_saml extension version is below 1.4.3 AND SAML configuration with sensitive credentials or private keys has been set up in the extension.

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

Upgrade the miniorange_saml extension to version 1.4.3 or later to remediate the sensitive data exposure. Review and rotate any credentials that may have been compromised.

Recommended fix High confidence

miniorange_saml version 1.4.3

  1. Check the currently installed version of the miniorange_saml extension in TYPO3 backend under 'Extension Manager'
  2. Create a complete backup of the TYPO3 database and files
  3. Update the miniorange_saml extension to version 1.4.3 or later using the TYPO3 Extension Manager or Composer (composer update miniorange/miniorangesaml)
  4. Clear all TYPO3 caches after the update
  5. Verify the new version is installed correctly in the Extension Manager
  6. Test SAML authentication functionality to ensure the update did not break existing configurations
  7. Review that API credentials and private keys are now stored securely per TYPO3 security best practices
Caveat Review extension release notes for any configuration changes required; minor version updates typically do not introduce breaking changes

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

Fix this in Saml Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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