dbcve.org
Oauth \& Openid Connect Single Sign OnDrupal extension · Miniorange

CVE-2024-13301

MEDIUM · 6.1 CVSS v3.1 Published 2025-01-09
Fix available
A fix is available. Upgrade to 3.44.0 / 4.0.19 or later.
See remediation →
68/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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Drupal OAuth & OpenID Connect Single Sign On – SSO (OAuth/OIDC Client) allows Cross-Site Scripting (XSS).This issue affects OAuth & OpenID Connect Single Sign On – SSO (OAuth/OIDC Client): from 3.0.0 before 3.44.0, from 4.0.0 before 4.0.19.

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

This is a stored Cross-Site Scripting (XSS) vulnerability in the Drupal OAuth & OpenID Connect SSO Client plugin. The plugin fails to properly sanitize user-supplied input during web page generation, allowing attackers to inject malicious JavaScript that executes in the browsers of other users who view the affected pages.

MitigationUpdate the OAuth & OpenID Connect Single Sign On (OAuth/OIDC Client) plugin to version 3.44.0 or 4.0.19 or later to remediate the XSS vulnerability.

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
Oauth \& Openid Connect Single Sign OnDrupal extension
Affected:>= 3.0.0, < 3.44.0>= 4.0.0, < 4.0.19

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Identify if the miniOrange OAuth/OIDC plugin is installed
    Check your Drupal site's installed modules list or the plugin directory for 'miniorange_oauth_client' or 'miniorange_openid_connect_sso'
    Affected if The plugin is not present in your installation, you are not affected by this CVE
  2. Find the installed plugin version
    Check the module's info file (miniorange_oauth_client.info.yml) or the Drupal admin interface under Extend > Installed modules > OAuth & OpenID Connect SSO Client for the version number
    Affected if The version number falls within 3.0.0 to 3.43.x OR 4.0.0 to 4.0.18 (inclusive)
  3. Verify the plugin is enabled and configured
    Check the module status in Drupal admin (Extend) and confirm whether OAuth/OIDC client configurations exist under Configuration > OAuth and OpenID Connect settings
    Affected if The plugin is enabled and has active client configurations - the XSS can be triggered through the plugin's input fields

If the miniOrange OAuth & OpenID Connect SSO plugin versions 3.0.0-3.43.x or 4.0.0-4.0.18 are installed and enabled on your Drupal site, you are affected by this stored XSS vulnerability.

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 3.44.0 / 4.0.19 or later
Fixed in 3.44.04.0.19
Interim mitigation

Update the OAuth & OpenID Connect Single Sign On (OAuth/OIDC Client) plugin to version 3.44.0 or 4.0.19 or later to remediate the XSS vulnerability.

Recommended fix High confidence

Upgrade to version 3.44.0 (if on 3.x branch) or 4.0.19 (if on 4.x branch)

  1. 1. Back up your Drupal site database and files before any updates
  2. 2. Update the OAuth & OpenID Connect Single Sign On (OAuth/OIDC Client) module using Composer: run 'composer update drupal/oauth_oidc --with-all-dependencies' or use the Drupal admin interface at /admin/modules
  3. 3. Clear Drupal caches by running 'drush cr' or via the admin interface at /admin/config/development/performance
  4. 4. Verify the updated module version is 3.44.0 or higher, or 4.0.19 or higher
Caveat Review release notes at www.drupal.org/project/oauth_oidc for any configuration or API changes between your current version and the target version

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

Fix this in Oauth \& Openid Connect Single Sign On Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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