dbcve.org
Saml Sp Single Sign OnWordPress extension · Miniorange

CVE-2022-4496

MEDIUM · 6.1 CVSS v3.1 Published 2023-01-30
Fix available
A fix is available. Upgrade to 12.1.0 / 16.0.8 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
The SAML SSO Standard WordPress plugin version 16.0.0 before 16.0.8, SAML SSO Premium WordPress plugin version 12.0.0 before 12.1.0 and SAML SSO Premium Multisite WordPress plugin version 20.0.0 before 20.0.7 does not validate that the redirect parameter to its SSO login endpoint points to an internal site URL, making it vulnerable to an Open Redirect issue when the user is already logged in.

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 SAML SSO WordPress plugins (Standard, Premium, and Premium Multisite) contain an open redirect vulnerability in their SSO login endpoint. The redirect parameter is not validated to ensure it points to an internal site URL, allowing authenticated users to be redirected to external malicious sites when they are already logged in.

MitigationUpdate the plugin to version 16.0.8 (Standard), 12.1.0 (Premium), or 20.0.7 (Premium Multisite) to obtain the fix that validates the redirect parameter points to an internal URL.

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 Single Sign OnWordPress extension
Affected:>= 12.0.0, < 12.1.0>= 16.0.0, < 16.0.8>= 20.0.0, < 20.0.7

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 installed Miniorange SAML SSO plugin variant
    Check the WordPress plugin directory for either 'miniorange-saml-20-sso', 'miniorange-saml-sso', or 'miniorange-saml-sp-sso' directories. Also check plugin name in wp-admin > Plugins.
    Affected if Any of these three plugin directories exist in the WordPress plugins folder.
  2. Retrieve installed plugin version number
    In WordPress admin, go to Plugins > Installed Plugins and find the version number listed under the plugin name. Alternatively, check the 'readme.txt' or main plugin PHP file header for the 'Version' field.
    Affected if A version number is found in the plugin files.
  3. Compare version against affected ranges
    Match the installed version to these ranges: Standard (Premium): >=12.0.0 and <12.1.0; Standard: >=16.0.0 and <16.0.8; Premium Multisite: >=20.0.0 and <20.0.7.
    Affected if The installed version falls into any of these three ranges.
  4. Verify plugin is active
    Check if the plugin status in WordPress admin Plugins page shows 'Active'. The vulnerability requires the SSO login endpoint to be accessible, which only works when the plugin is active.
    Affected if The plugin is currently activated on the WordPress site.

A user is affected if they have any Miniorange SAML SSO plugin variant (Standard, Premium, or Premium Multisite) active with a version matching the affected ranges: 12.0.x, 16.0.x through 16.0.7, or 20.0.x through 20.0.6.

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 12.1.0 / 16.0.8 / 20.0.7 or later
Fixed in 12.1.016.0.820.0.7
Interim mitigation

Update the plugin to version 16.0.8 (Standard), 12.1.0 (Premium), or 20.0.7 (Premium Multisite) to obtain the fix that validates the redirect parameter points to an internal URL.

Recommended fix High confidence

Upgrade to SAML SSO plugin version 12.1.0, 16.0.8, or 20.0.7 depending on your current major version branch

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. Find the SAML SSO Sp Single Sign On plugin
  4. Update the plugin to version 12.1.0 (for versions 12.0.x), 16.0.8 (for versions 16.0.x), or 20.0.7 (for versions 20.0.x)
  5. Verify the update was successful by checking the plugin version
Caveat Standard WordPress plugin update; test SSO functionality after upgrade to ensure SAML authentication still works correctly

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

Fix this in Saml Sp Single Sign On Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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